|
|
|
|
|
by ruslan_talpa
2426 days ago
|
|
Have you looked into postgrest's "select" parameter?
Your comment about the "scope" of the query applies here too. Also GraphQL is a protocol and you can't really say it will have poor performance, it all depends on the specific implementation of a particular schema. You can have a GraphQL schema where each query gets translated into a single sql query [1] jsut like with postgrest. One thing that is true is that the reference implementation for graphql servers (but only because it has to be general) pushes one in a direction where a single graphql request might generate a storm of sql queries but it's on developer to understand and write proper resolvers. [1] https://github.com/subzerocloud/subzero-starter-kit |
|