3 ms·
Well, database introspection isn't new, we could've done that decades ago, but there are good reasons for the layer of abstraction. Also if you go down this ro
by lyu07282 2y ago
Well, database introspection isn't new, we could've done that decades ago, but there are good reasons for the layer of abstraction.
Also if you go down this route, I think Postgraphile is a much better realization of that idea (uses GraphQL, not REST): https://www.graphile.org/postgraphile/ https://www.graphile.org/postgraphile/
- dventimi 2y agoI see no particular reason to believe that Postgraphile, while a good tool, is any better (or any worse) than PostgREST, just as I see no reason to believe GraphQL is better than REST. As for layers of abstraction, one can have layers of abstraction with PostgREST: views and procedures.
- lyu07282 2y agoIt's not better because it's gql, it's better because it's more feature complete (like RLS), offers more/easier customization, isn't written in Haskell, etc., but ofc your milage may vary. > As for layers of abstraction, one can have layers of abstraction with PostgREST: views and procedures. I can't even imagine a more closely coupled and leaky abstraction than views and procedures in a database
- dventimi 2y agoThe database has RLS, and I don't care what PostgREST and Postgraphile are implemented in, so personally I'm unmoved by these two claims. As for things we're unable to imagine, what I can't imagine is how table structure (for example) could possibly leak through a view or procedure. You're welcome to try to explain it, though you're not obliged to.
- fzeindl 2y agoThanks for your comment, I will look into postgraphile.