postgraphile-plugin-connection-filter VS graphjin

Connection Filter Plugin

For example:

https://github.com/graphile-contrib/postgraphile-plugin-conn...

and

https://github.com/graphile/pg-aggregates

Have a look at PostGraphile (in case you are using JavaScript and a PostgreSQL DB). With the advanced connection filter plugin (https://github.com/graphile-contrib/postgraphile-plugin-connection-filter) you get an automatically created filter for multiple items and their connection.

The postgraphile-plugin-connection-filter I referred to is up-front about the fact that the filters it generates could allow a caller to form queries that would bring your server to its knees. So I'd have to do some work to limit what predicates were allowed.

More examples here: https://github.com/graphile-contrib/postgraphile-plugin-conn...

(Personally, I think their docs are good at telling you how to use it but fairly bad at showing how great the tool is)

I really line the approach used here https://github.com/graphile-contrib/postgraphile-plugin-connection-filter

This one looks interesting if you like GraphQL… https://graphjin.com

You're right. Django made a ton of tables, and it's pretty insightful to think about all the stuff it's trying to consider and a nightmare to migrate that framework. Django might have simplified some stuff, but it's still too opaque for my taste and the overall end goals of the project. Currently, I'm testing using graphjin (it doesn't have the best documentation, but it does boast an SQL generation capability that I philosophically think is the best way to do things).

Checkout GraphJin it's an automatic GraphQL to SQL compiler, you write your database queries in GraphQL instead of SQL and it compiles them into efficient SQL on the fly. Works as a library in GO and NodeJS. https://github.com/dosco/graphjin

In GraphJin an automatic GraphQL to SQL compiler we use the gnomock library it startups a database instance (docker) then create the schema and tests data and finally our code connects to it and runs a series of tests. We run these across Mysql, Postgres and a few other DB's. Gnomock supports a wide range of them. Right now we don't take down the db for every test only between test runs but its fast enough that we could. This whole thing runs of a simple `go test -v .` command and we run it on every commit using a githook. https://github.com/dosco/graphjin/blob/master/tests/dbint_te...

This was a bug in GraphJin it has since been fixed. The issue was that you were trying to have multiple subscriptions over a single websocket this did not work (it should) and now it does. https://github.com/dosco/graphjin/commit/43e619b2ff392dd42b99a4d56074a041a54b0e1c

Not exactly GraphQL is just a format to define what data you want back from someplace. You can use it in a browser app to request data from a backend GraphQL server or you can use it as an ORM within your backend app to fetch data from a database using a library like GraphJin. https://github.com/dosco/graphjin