I'm trying to build a simple web app on Supabase that uses GraphQL on the front end. The catch is that my Postgres database needs to support translations (using JSONB), but apparently Supabase doesn't support querying those translations or implementing custom GraphQL resolvers. Any suggestions?
Currently debating between hosting my database elsewhere, or abandoning GraphQL for REST.
[#]supabase #graphql #i18n #opensource #postgres #jsonb #webdev #appdevelopment
=> More informations about this toot | More toots from dzso@mastodon.social
@dzso I hate GraphQL, everywhere I've seen it in use, it's added to both the developers' and the DBAs' workload instead of making things easier. And of course made performance worse
=> More informations about this toot | More toots from vyruss@fosstodon.org
@vyruss In theory, it seems nice. But I've never had a full stack GraphQL setup that was painless. There's always some part of the workflow that's underdeveloped.
=> More informations about this toot | More toots from dzso@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini