Re:Why not use GraphQL?
by odshoifsdhfs on Saturday November 07, 2020 @08:51AM
(#25015067)
I created a no-code tool that could do joins, filters, and more with GraphQL, so I really don't see your point. You just need to do it a bit differently (same as REST, and if you follow REST 100%, good luck with n*m calls when you want to join two resources that you don't know from the start):
GET clients [client 1, client 2]
for each client
GET business (id = client.id)
Now think you can join with business, jobs, invoices, employees, etc etc, and tell me how to do this in rest without basically recreating a query language?
Re:Why not use GraphQL?
by codegladiator on Saturday November 07, 2020 @10:27AM
(#25015578)
Try to build an aggregate API over graphql. Where all sql functions are allowed on appropriate columns.
Re:Why not use GraphQL?
by odshoifsdhfs on Saturday November 07, 2020 @07:11PM
(#25021238)
I did, the same way you would do with a REST API. you specify a format for a field (in my case, the 'where' and 'join' where JSON structures that you passed as parameters)
Then you write the resolvers that parse that. Pretty much as I would expect you to do it in REST.
(mentioned it in another post, I created a no-code tool that did this, for random data and entities created by the user per tenant/app, so I know the issues with GQL, but I can assure you, doing the same with REST was 10 times harder (api started as REST and moved to GQL after 6 months)
Re:Why not use GraphQL?
by philplckthun on Saturday November 07, 2020 @08:20AM
(#25014910)
That’s a pretty misleading statement, since what you’re linking to does describe how using scalars can help.
Especially if the scalar never includes other data from the graph (other objects) describing the custom format with scalars is just fine.
https://stackoverflow.com/questions/45842544/graphql-objectt...
In REST, I can send the columns and know what I am going to get back. All the queries need not be defined to start with.