Anyone running projects with just Next.js + Supabase and no traditional backend?
I tried to make this work for me, but I finally gave up this week and wrote a traditional backend component for part of my backend because supabase doesn't support transactions and I am NOT going to write my whole backend in postgres functions.
Supabase-JS v2
61–70 of 82 posts
Re: Supabase-JS v2
#62Re: Supabase-JS v2
#63In their FAQs they argue that you can just use JSON columns in Postgres but that doesn't really solve my issue because those columns would still need to be pre-defined.
Re: Supabase-JS v2
#64Re: Supabase-JS v2
#65Re: Supabase-JS v2
#66(i’m the github complainer)
Re: Supabase-JS v2
#67I really love Supabase and I would consider it for my new project but I have a requirement to be schemaless, I know the reasons why they chose Postgres, those are explained clearly on their website, but I wish they added a NoSQL DB as an alternative at least. In their FAQs they argue that you can just use JSON columns in Postgres but that doesn't really solve my issue because those columns would still need to be pre-…
Re: Supabase-JS v2
#68How do you limit the queries allowed in the UI aka prevent someone from making a really slow / large query? Do you general not use supabase directly in the UI and write an API that your front end can call instead?
You can also be fully restrictive by only allowing the client to call the custom SQL functions[2] you define. In Supabase this is done by having all your tables in a "private" schema and only SQL functions in the "public" schema(whose db objects get exposed to the client).
[1]: https://postgrest.org/en/stable/api.html#custom-queries
Re: Supabase-JS v2
#69Re: Supabase-JS v2
#70I know Supbase is a sponsor of the PostgREST.