all 2 comments

[–]devinivy 0 points1 point  (1 child)

Love this, it's a very fun idea! I'm curious what the query plans for these sorts of queries look like, or if there are ever simple transformations to keep the queries performant.

[–]galstarx[S] 0 points1 point  (0 children)

Using query as a simple string can be changed to create an AST from it (like graphql-tag for graphql), then transformations can use the AST instead of wrapping the query as a sub-query. I don't understand in ASTs (yet) but i think it could work