We’re overhauling Dgraph’s docs to make them clearer and more approachable. If
you notice any issues during this transition or have suggestions, please
let us know.
This is part 1 of Building a To-Do List App.
- Task
- User

Task
type. Then the User
type has a username (unique identifier), name and the
tasks.
So each user can have many tasks.

’ * ’ signifies one-to-many relationship
@id
directive to username
which makes it the unique key & also
add @hasInverse
directive to enable the relationship between tasks and user.
We represent that in the GraphQL schema shown below:
schema.graphql
.
Running
Before we begin, make sure that you have Docker installed on your machine. Let’s begin by starting Dgraph standalone by running the command below:http://localhost:8080/graphql
. If you know
lots about GraphQL, you might want to explore the schema, queries and mutations
that were generated from the schema.
Mutating data
Let’s add a user and some to dos in our To Do app.Querying data
Let’s fetch the to dos to list in our To Do app:Querying data with filters
Before we get into querying data with filters, we’re required to define search indexes to the specific fields. Let’s say we want to run a query on thecompleted
field, for which we add
@search
directive to the field, as shown in the schema below:
@search
directive is added to support the native search indexes of
Dgraph.
Resubmit the updated schema -
title
field, for which we add
another @search
directive to the field, as shown in the schema below:
fulltext
search index provides the advanced search capability to perform
equality comparison as well as matching with language-specific stemming and
stopwords.
Resubmit the updated schema -