Re:How to GraphQL – A Fullstack Tutorial for GraphQL
by vosper on Tuesday July 11, 2017 @08:18PM
(#14749194)
What about using GraphQL implies that you're trying to map objects from the database? As far as I know you can just query for the fields you want (with whatever joins you might need, or subqueries, or calls out to some other system) and return them to the client.
Re:How to GraphQL – A Fullstack Tutorial for GraphQL
by slaymaker1907 on Saturday July 15, 2017 @11:45PM
(#14780362)
It's doing object mapping because it is coercing everything into JSON. Looking at the language, you see the usual suspects of strange cyclic objects for representing relations typical of ORMs. These systems tend to struggle when dealing with things like many to many relationships, non-total relations, etc. To give it credit though, I do like that GraphQL forces a firm separation between remote and local data, though I'm sure there are already libraries for GraphQL trampling over that separation.
Re:How to GraphQL – A Fullstack Tutorial for GraphQL
by ruslan_talpa on Tuesday July 11, 2017 @06:46PM
(#14748727)
there is, PostgreSQL
https://blog.2ndquadrant.com/application-users-vs-row-level-...
(and saying GraphQL can't work with databases I think is wrong, it's the same as saying OO languages are not a good fit for relational databases)
Re:How to GraphQL – A Fullstack Tutorial for GraphQL
by slaymaker1907 on Saturday July 15, 2017 @11:46PM
(#14780366)
Thanks for the info!
Ideally, you'd be able to just handle these security issues with the database directly through views and permissions, but as far as I know there is no database with enough permissions controls for this.