The docs shows this way of definining a schema once
type Person {
name string
}
type Car {
regnbr string
owner Person
}
owner uid @reverse .
regnbr string @index(exact) .
name string @index(exact) .
and most other times it would do something like this
type Person {
name
}
type Car {
regnbr
owner
}
owner: uid @reverse .
regnbr: string @index(exact) .
name: string @index(exact) .
Does it make any difference ? Why are there no other references in predicate types inside types apart from here https://dgraph.io/docs/query-language/schema/# (with no explanation about it)
Why do I have to declare a predicate for every single subtype field ? That’s a lot of duplication
I’m having a hard time trying to understand whats the most common or right way to do stuff with dql, the DQL section starts off with a lot of info on functions/filtering/whatever when I still haven’t understood how am I supposed to correctly make a schema
Some more complex graphql to dql schema comparison would be great as well
same here, the docs are very slim. i am very greateful for the amazing Learn courses. But it wouldn’t be bad to update the docs and explain more things and do more examples (good docs are a very important thing, they are really way to slim), and add a comment section (which is a discourse post just inline linked), and add the 123456 (look at picture) lines so that we can better tell which lines at the docs we mean
also it would be cool to have this feature like googles help sites have, so that we can ask/comment-on-posts more directly about issues. that helps a lot for people like amaster and michel to help quicker and save time
If you’re confused or stuck with anything there are plenty of people who can help, feel free to ping me. There’s also an (unofficial) Discord channel where you can ask questions: https://discord.gg/DkFKDfzTZz
if anyone has the same error in the second picture:
solution: you have to go into your discord app and click on the PLUS and then insert the invite link there