Supabase does not make sense sometimes
It gets messy very fast if you need any complex logic, which is why business logic almost always ends up on the application server in a traditional stack, not the DB.
2 comments
This was my original complaint with database triggers. It ends up breaking where your important code exists.
However we're entering an age where database + authorization may be more and more available as an all-in-one solution. More vendors are realizing that REST style services are just a facade over a database anyway - so why have an application server?
However we're entering an age where database + authorization may be more and more available as an all-in-one solution. More vendors are realizing that REST style services are just a facade over a database anyway - so why have an application server?
testing database triggers is a pain, i can change one line of code logic in server and hit ctr+s then i test the api faster than testing db trigger function + it is more readable in one place
[deleted]