Pg_GraphQL: A GraphQL Extension for PostgreSQL
supabase.com
Pg_GraphQL: A GraphQL Extension for PostgreSQL
1–10 of 102 posts
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#2Curious how it compares to https://www.graphile.org/postgraphile/
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#3Curious how it compares to https://www.graphile.org/postgraphile/
The article suggests they built it so that by running it within the DB it would have less compute overhead and they could match GraphQL requests to SQL transactions 1:1.
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#4How long before someone just goes into the Postgres source code and creates true native support for GraphQL
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#5That’s interesting. How does it deal with authentication and authorization? It it handles those well, it could be a real “serverless” solution for most CRUD apps.
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#6That’s interesting. How does it deal with authentication and authorization? It it handles those well, it could be a real “serverless” solution for most CRUD apps.
They mention in the article that auth is handled by reusing the existing row level security you'd already use to secure the DB (i.e. `CREATE POLICY`).
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#7author here! happy to answer questions
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#8I've been using Hasura extensively and love it. I'm curious what the delta is between the two. It's so simple to run Hasura on dokku and instantly get an amazing UI for postgres with the bonus of graphql. It would take a lot for me to switch.
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#9How long before someone just goes into the Postgres source code and creates true native support for GraphQL
An extension is the best next thing to native support and in my opinion a better place for such functionality.
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#10That’s interesting. How does it deal with authentication and authorization? It it handles those well, it could be a real “serverless” solution for most CRUD apps.
The extension is compatible with your existing row level security policies. If you connect to the database as a role like `authenticated` then those policies will be applied.
The columns and tables that are visible are also controlled by the role.
One cool thing about that approach is you could run e.g. an admin API and a user facing API all from that same endpoint by executing as different postgres roles!