Dgraph APIs
Execute queries and mutations against a Dgraph database
While each Modus SDK offers similar capabilities, the APIs and usage may vary between languages.
Modus Dgraph APIs documentation is available on the following pages:
- AssemblyScript Dgraph APIs (this page)
- Go Dgraph APIs
The Modus Dgraph APIs allow you to run queries and mutations against a Dgraph database.
Import
To begin, import the dgraph
namespace from the SDK:
Dgraph APIs
The APIs in the dgraph
namespace are below, organized by category.
We’re constantly introducing new APIs through ongoing development with early users. Please open an issue if you have ideas on what would make Modus even more powerful for your next app!
Functions
alterSchema
Alter the schema of a Dgraph database.
Name of the connection, as defined in the manifest.
The schema to apply to the Dgraph database.
dropAll
Drop all data from a Dgraph database.
Name of the connection, as defined in the manifest.
dropAttr
Drop an attribute from a Dgraph schema.
Name of the connection, as defined in the manifest.
The attribute to drop from the Dgraph schema.
escapeRDF
Ensures proper escaping of RDF string literals.
The RDF string literal to escape.
executeMutations
Execute one or more mutations, without a filtering query.
If you need to filter the mutations based on a query, use the
executeQuery
function instead, and pass the mutations after
the query.
Name of the connection, as defined in the manifest.
executeQuery
Execute a DQL query to retrieve data from a Dgraph database.
Also used to execute a filtering query and apply one or more mutations to the result of the query.
If you need apply mutations without a filtering query, use the
executeMutations
function instead.
Name of the connection, as defined in the manifest.
Optional parameters specifying one or more Mutation
objects to
execute on the nodes matched by the query.
Types
Mutation
A Dgraph mutation object, used to execute mutations.
Creates a new Mutation
object with the given setJson
, delJson
,
setNquads
, delNquads
, and condition
fields.
A JSON string representing the data to set in the mutation.
A JSON string representing the data to delete in the mutation.
A string representing the data to set in the mutation in RDF N-Quads format.
A string representing the data to delete in the mutation in RDF N-Quads format.
A string representing the condition query for the mutation, as a DQL @if
directive.
Sets the setJson
field of the mutation to the given json
string. Returns
the Mutation
object to allow for method chaining.
Sets the delJson
field of the mutation to the given json
string. Returns
the Mutation
object to allow for method chaining.
Sets the setNquads
field of the mutation to the given nquads
string.
Returns the Mutation
object to allow for method chaining.
Sets the delNquads
field of the mutation to the given nquads
string.
Returns the Mutation
object to allow for method chaining.
Sets the condition
field of the mutation to the given cond
string, which
should be a DQL @if
directive. Returns the Mutation
object to allow for
method chaining.
Query
A Dgraph query object, used to execute queries.
Creates a new Query
object with the given query
and variables
. query
is a Dgraph Query Language (DQL) query string, and variables
is an optional
Variables
object.
The DQL query to execute.
A map of query variables, with values encoded as JSON strings.
Sets a query variable with the given name
and value
. name
is of type
string
, and value
can be a string, number, or boolean.
Returns the Query
object to allow for method chaining.
The withVariable
method is the preferred way to set query variables in a
Query
object, and allows for fluent method chaining to add multiple variables.
For example:
Request
A Dgraph request object, used to execute queries and mutations.
This object was used by the execute
function, which has been replaced by the
executeQuery
and executeMutations
functions. You should no longer need to create a Request
object directly.
Variables
A Variables object used to set query variables in a Dgraph query.
As of SDK version 0.17.1, it’s no longer necessary to explicitly create a
Variables
object. Instead, use the withVariable
method on the
Query
object to set query variables.
Sets a query variable with the given name
and value
. name
is of type
string
, and value
can be a string, number, or boolean.
Returns a map of all query variables set in the Variables
object, with
values encoded as strings.
Was this page helpful?