[lorenzotenti]

Are we repeating history though? I've worked for a company that used Oracle plsql for everything (shall we return html snippets from the database as a reactive frontend, why not!, the whole business logic is in huge stored procedures anyway) and it was clearly an utter mess. Now, new tools may make this better, but every time I see too much business logic getting close to SQL I get suspicious. Supabase is another example of doing everything with postgres. Sounds cool, but is it maintainable?

[brtkdotse]

Tangentially, it’s curious there hasn’t emerged A Proper Way of version controlling and deploying stored procedures outside of “stick a bunch of sql scripts in a folder in the project root”

[vanviegen]

Is there anything wrong with that approach? It seems pretty optimal to me, since you'll probably want to commit the stored procedures together with regular code.

[brtkdotse]

Not really! It’s just weird that every places I’ve worked at basically invents it from first principles rather knowing about it.

[eddd-ddde]

Exactly, the reason the other alternatives feel better, is not because of how they work, but because of the tooling.

[city41]

Supabase now has edge functions: https://supabase.com/edge-functions