Skip to content
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

Open
ghost opened this issue Aug 29, 2018 · 5 comments
Open

query language #2

ghost opened this issue Aug 29, 2018 · 5 comments
Labels
question Further information is requested

Comments

@ghost
Copy link

ghost commented Aug 29, 2018

Is there any plan to incorporate a query language ?

@dennwc
Copy link
Member

dennwc commented Aug 29, 2018

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.

@ghost
Copy link
Author

ghost commented Aug 30, 2018

Could we discuss ?

Is the query language strong or weak typed ?
Is a graphql with dynamic resolvers via a AST parser on the cards ?
There are already many good graphql parsers using AST.

@dennwc
Copy link
Member

dennwc commented Aug 30, 2018

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.

@ghost
Copy link
Author

ghost commented Sep 1, 2018

thanks @dennwc
Sounds great !
Is there any code in cayley to use hidalgo yet ? Would like to explore what i can do with hidalgo and graphql.

@dennwc dennwc added the question Further information is requested label Sep 2, 2018
@dennwc
Copy link
Member

dennwc commented Sep 2, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant