-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
query language #2
Comments
Yes, the main intention is not only to provide read-write abstraction but also allow to build complex queries that backends can optimize to any native query language that is supported. I will leave this issue open until it's clarified in the README. |
Could we discuss ? Is the query language strong or weak typed ? |
The plan is to support at least SQL and GraphQL. At least on the tuplestore level, the query language can be strongly typed (schema is known). And yes, I already implemented a dynamic GraphQL for Cayley that uses an AST to build a query plan instead of calling resolvers. |
thanks @dennwc |
The code in questions can be found here: https://github.com/cayleygraph/cayley/tree/master/query/graphql, but it's only useful for Cayley. May serve as an example how to write the similar query planner, though. There is also a branch in Cayley that works with Hidanlgo, but it only uses the KV layer, not the tuple-store. In any case, I'm leaving this open to serve as a starting point for further discussions. |
Is there any plan to incorporate a query language ?
The text was updated successfully, but these errors were encountered: