We already support user defined PG functions to be exposed as graphql queries so this is a natural extension.
499 karma · joined November 22, 2015
We already support user defined PG functions to be exposed as graphql queries so this is a natural extension.
I agree 100%. The hardest general books are probably in the area of philosophy. My recent fav: The Logic of Scientific Discovery by Karl Popper.
I think it would be more correct to just say that GraphQL encourages queries as first class object as it exposes the entire schema and allows for granular querying.
Implementing it by composing REST APIs is, well, an implementation detail. There are other ways to do it too.
This thread is quite timely as we recently published a post about this here: https://hasura.io/blog/fast-graphql-execution-with-query-cac...
https://blog.hasura.io/remote-joins-a-graphql-api-to-join-da...
https://blog.hasura.io/graphql-and-geo-location-on-postgres-...
PS: I work here. Apologies for plug.
Except nobody bought. A car is more than its functionality. It is also a symbol.
See The Blub Paradox [0]
Single loop when I know the domain fairly well. And double loop in a complete new domain.
So, the question is: Are there other methods to approach problem-solving which gives positive success?
What now? Fields are just one part of versioning problem.
All the best.
Ref page 8-9 in [1]
[1] https://www.microsoft.com/en-us/research/publication/beautif...