Re:Graphql-Up: CLI to create a ready-to-use GraphQL API
by ruslan_talpa on Wednesday March 15, 2017 @04:00AM
(#13874534)
You are dismissing a valid question and incidentally this is the question that exposes a problem of the graphql-js implementation (specifically the execution module) when the data source is a database (which 90% of the time it is), though it's not a problem of the GraphQL . Of course he can not "well-forme" it since he is just looking into GraphQL.
What he is looking for actually is this https://github.com/stems/join-monster but it's not without it's problems.
PS: My comment does not mean the reference implementation is bad, it's just that it's a reference and good in a lot of cases but not in all. It does not mean you have to use every part of it, you can write your own execution module.
So asking how to do a join in GraphQL is like asking how to do a join in REST. It's not a well-formed question.
The good news is that the sever can expose absolutely anything as a GraphQL query. They're just arbitrary entry-points into the schema. Think of it as like calling a stored procedure. The procedure is an opaque thing as far as the caller is concerned.