First, to be clear - I'm not talking about moving the whole application layer to the DB. Sometimes, I think moving some of it can be a viable option. I did a f

First, to be clear - I'm not talking about moving the whole application layer to the DB. Sometimes, I think moving some of it can be a viable option. I did a fair bit of T-SQL back in the day. You're right: it's not fun. It's okay for shuffling data around and doing SQL-y things in a slightly procedural way. Inserting rows, copying rows. For anything complex... well, it's not made for that. But even SQL Server lets you call .NET CLR code now: https://learn.microsoft.com/en-us/sql/relational-databases/stored-procedures/stored-procedures-database-engine?view=sql-server-ver16 https://learn.microsoft.com/en-us/sql/relational-databases/s... And of course Postgres supports Python, etc etc etc.