6 ms·
Isn't that what the ActiveRecord pattern is supposed to be? (Something something n+1's and over fetching data.)
by N_A_T_E 4y ago
Isn't that what the ActiveRecord pattern is supposed to be? (Something something n+1's and over fetching data.)
- eurasiantiger 4y agoIf only we had a generic GraphQL resolver for entity-based SQL schemas. Oh wait, we do have Prisma. And it suffers from those same issues.
- drpotato 4y agoHave you looked at PostGraphile? It’s doesn’t have n + 1 or over-fetching issues.
- eurasiantiger 4y agoI have, and I would recommend it, if it generated a Postgre schema from a GraphQL schema and not the other way around. The advantages of GraphQL are its integration of backend and frontend workflows, and that won’t happen with PostGraphile: a frontend needing a schema change needs to go through the backend instead of the backend extending to meet the frontend in the middle.