I think I’m conflating concepts together because this is new to me.
Most of my focus, at the moment, is understanding the flavor of GraphQL (GraphQL±) produced by the company Dgraph. However, given some of the other documentation, I’m also interested in understanding the “pure” GraphQL option (if I understand that correctly).
Basically, here are a few points related to the query languages:
- What is the difference between “regular” GraphQL and GraphQL±?
- If there’s a notable difference, is it only possible to use the supported clients (e.g. Go) to run GraphQL queries/mutations and not “regular” GraphQL?
- The documentation resources you shared in your last response were helpful - can you help me understand the difference between the documents discussing the Dgraph query language?
- I’m definitely interested in the documentation you provided because defining the schema in “pure” GraphQL seemed to be more in-line with what I’m looking for where types are explicitly linked as predicates on other types in the definition.
On the database side:
- The “primary” endpoint on a Dgraph database seems to be geared towards receiving GraphQL± queries while the
/graphqlendpoint is designed to receive “regular” GraphQL - is that correct? - Understanding this difference and the trade offs (if there are any) is something I’d definitely like.
To answer your question:
This feels like a Dgraph question. Can you confirm this?
Yes, as far as my only recent understanding of the concepts, it is a Dgraph question.
To answer your other question:
Another question, have you used Dgraph or Dgraph’s GraphQL before?
Yes, I’ve followed the tutorials and spun up local Dgraph databases in Docker and interacted with the database vai the Ratel UI.
Thank you very, very much for your responses - it’s helping me to understand better this too. Once I get better acquainted with the project, I’d love to contribute to the Go client on GitHub!
Best,
John