I built a supabase app the past two days, and I agree. I did find it a footgun that creating a table through SQL was not private by default. (Why doesn't Supab

I built a supabase app the past two days, and I agree. I did find it a footgun that creating a table through SQL was not private by default. (Why doesn't Supabase apply RLS by default to tables created through SQL?) Serverless also turned out to be more trouble than it was worth. In particular: * Doing DB business logic in JS is gross. * It's tricky to secure a table to be semi-public. e.g. you have a bookmark site and you don't want users to browse all URLs, just the ones they have bookmarked. The best solution appears to be disabling foreign-keys until transactions are done and then having a complicated policy. * It's a pain to set up a CLI client that interacts with the DB. I think you have to copy-paste the access AND refresh tokens to it. I couldn't figure out a way to create my own API tokens. A backend is nice, because it is private by default.