How does it compare to Apache Age?
Apache Age is based around the openCypher graph query language rather than GraphQL
Pg_GraphQL: A GraphQL Extension for PostgreSQL
31–40 of 102 posts
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#32How does it compare with https://github.com/solidsnack/GraphpostgresQL ? It's like 7 years older and it takes the same approach, it seems.
Very cool! I was not familiar with this project. It does takes a similar approach to query building. It is described in the README as an alpha POC
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#33There is no way every cloud provider won't jump on this as soon as it's stable for their Postgres offerings.
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#34author here! happy to answer questions
So you're calling Graphql via PostgREST, but I didn't ready about why you're including Graphql in the first place. Isn't it orthogonal to PostgREST which is already used in your stack?
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#35author here! happy to answer questions
Congrats on release. We use Hasura but haven’t been happy with their speed of iteration, lack of communication of various large bugs, and lack of M1 support / communication. But we do use a lot of their more advanced features like being able to use aggregates in sorts, aggregates in results, custom functions, etc. What are your plans there and will you have a public roadmap?
There is high level public roadmap that covers the minimum features required before we'd consider going GA here:
https://supabase.github.io/pg_graphql/roadmap/
Its early days, so the conversations around aggregates haven't happened yet, but I'm optimistic that they'll make an appearance in a future release
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#36author here! happy to answer questions
I've been looking for something like this for a long time, so cool! Great work!
Does it work with TimescaleDB?
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#37PostgreSQL has the great shiny features, but still doesn't support zero downtime upgrades?
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#38How does it compare with https://github.com/solidsnack/GraphpostgresQL ? It's like 7 years older and it takes the same approach, it seems.
Very cool! I was not familiar with this project. It does takes a similar approach to query building. It is described in the README as an alpha POC
[deleted]
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#39As co-founder of another database company in the PostgreSQL ecosystem, I have to say that I'm really impressed with the quality and velocity of launches from the Supabase team. Nothing else to add, except please keep up the great work!
What's your company?
Re: Pg_GraphQL: A GraphQL Extension for PostgreSQL
#40I use Dgraph, a "native" GraphQL DB. But I still transform the incoming/outgoing JSON to Java object and transforming the object again to/from the DB. Why? 2 things: Business Logic and Security/Access Control. Yes I can put (some) Business Logic in Dgraph DB, but it feels "leaky" like Stored Procedure (maybe because I come from Java). I feel it's tiring and stupid, but I don't know a better solution.
I reckon for this extension, the business logic uses Stored Procedure and Access Control uses PG's user role? Many apps I know simply have 1 user "myappuser" (or even default user) to access its DB.