crystal

I didn't see a v5 tag in order to know, and I have no idea what "utils/graphile" does for the project, but one will want to ensure they are aware of its licensing scheme https://github.com/graphile/crystal/blob/db8894c74eb0ec3fe96...

I was about to say “but this one is!” and realized I had confused PostgREST with PostGraphile. If you’re interested in GraphQL, you can check out PostGraphile here: https://github.com/graphile/postgraphile It’s interesting to me that PostgREST and Hasura are written in Haskell, but PostGraphile is not. Given the complexity in parsing arbitrary GQL queries I think I assumed that Haskell was a better fit for the job, hence the mixup!

What do you mean locally? Hasura is OSS, and you can run it locally (you have autogenerated SQL statements) Here you can just use Nhost and its CLI; Alternatives are https://github.com/graphile/postgraphile or dgraph as you mentioned. Hasura is working on support for sqlite, so you may have some blockers there, you can also look into the Prisma engine which has GQL as an intermediate (for resolvers, for example)

I've personally found Postgraphile to be fantastic. Nicer to use than Hasura and fully OSS: https://github.com/graphile/postgraphile/

Hi all, this sounds very cool. How does pg_graphql compare to Postgraphile? https://github.com/graphile/postgraphile (besides I guess running in the DB with PLpgSQL instead of as a NodeJS server) Did you think about integrating Postgraphile with the Supabase ecosystem or have specific limitations with it? Thanks!

This is cool but sadly looks abandoned. Here's an active project that does something similar (introspects your postgres schema and runs a graphql API on top): https://github.com/graphile/postgraphile Prisma is also interesting (but pulls more logic out of the DB). My question with this type of logic-in-the-DB framework is how people are managing schema migrations and what infra they're running on as it's clearly a little less charted than, for instance, deploying a rails app (what I know). I really like the DRYness of writing the schema in one place and having that flow automatically into strongly typed models, API, etc with correct auth logix. This always seems like too much boilerplate with ActiveRecord and controllers.

Postgraphile https://github.com/graphile/postgraphile It's like Hasura but written in a language you can understand. Using it with great success on two projects, both > 3 months into development on.

You might find Postgraphile interesting, if you like graphql: https://github.com/graphile/postgraphile

I considered Hasura but went with postgraphile (https://github.com/graphile/postgraphile) because it's written in JavaScript with a plugin architecture, meaning I can easily add my own plugins into the system down the road. Creating a JavaScript plugin sounds much less daunting that looking into a mature Haskell codebase.

This is cool, although these days, (if requirements permit), my choice would be GraphQL via something like PostGraphile. https://github.com/graphile/postgraphile

For someone looking for a GraphQL solution, which benefits does EdgeDB have over https://github.com/graphile/postgraphile ?

> I haven't seen a single backend framework which doesn't actively encourage an N+1 problem on any query which returns multiple objects of data Well then you haven't really looked :) https://join-monster.readthedocs.io/en/latest/ https://github.com/graphile/postgraphile https://www.prisma.io/ https://subzero.cloud/ These are all examples of tools/libs that implement a graphql api without a N+1 issue

Yes and I love it, and it’s amazing. I have been using it to write plpgsql functions for postgraphile. Find out more at https://github.com/graphile/postgraphile

I recently tried Postgraphile [1] on an existing postgres database (briefly just for fun, not in prod) and it sort of does what you want. As long as the foreign keys are there, it will generate the correct graphql queries. It even pluralizes the query names depending on whether it's a one-to-one or one-to-many relationship. Once it's in graphql you can just use the interactive graphql endpoint which has autocomplete and documentation to write your queries. A schema like: create table post ( id serial primary key, author_id int non null references user(id), headline text, body text, ... ); Can query relations like so: allPosts { edges { node { headline body author: userByAuthorId { name } } } } [1] https://github.com/graphile/postgraphile/tree/post