postgraphile-plugin-connection-filter VS pgress

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

Hey Marco, I'll take a look - filters theoretically should be fast, when you create a new filter, it simply reads does a `select * from table limit 1` to get column names

I wasn't sure whether you could query DBs directly from the browser but looks like you can! (https://github.com/alexanderguy/pgress) - will add it to roadmap!

I had fun with a similar concept: just access the database from the browser using nginx/TLS/lua: https://github.com/alexanderguy/pgress

If you're good with your authenticated users directly talking to the DB (which there are plenty of uses for), it's a great way to get your data into the browser.