2 ms·

Nearly every system I worked on that had significant business logic in SQL turned out to be a maintenance nightmare. Used to be a lot of this in the 90s or earl

Nearly every system I worked on that had significant business logic in SQL turned out to be a maintenance nightmare. Used to be a lot of this in the 90s or early 2000s. Where dB venders encouraged it for obvious reasons. SQL isn't built with sensible decisions. Delete/update forget a where clause? Whoops. Lots of traps like that. Also it's not easily testable. Domain concepts don't always easily map.

primeblue 4y ago
alexvoda 4y ago
Part of the reason is that SQL is simply a bad language (the JavaScript of databases). Part of the reason is also the thinking and philosophy behind DBMSs as interactive systems. Especially with regards to code. A function doesn't just exist. You create a function and it lives in the database until you alter it or drop it. This creates a different (temporal?) impedance mismatch with standard code management tools like version control. The result is most often a maintenance nightmare.