|
|
|
|
|
by whizzter
233 days ago
|
|
I haven't had the "pleasure" to work with stored procedures,etc but from conversations the main takeaways seems to be: 1: cooperation, nowadays database instances are cheaper and with Docker we can spin them up but having them shared doesn't feel like a fun thing when developing (triggers more than stored procedures here) 2: version control, kinda ties to the above but being able to keep track of changes (and related then to code being out of sync even if that would matter less in a application-less world) 3: debugging in general ? 4: debuging "spooky effects at a distance" when triggers,etc run. What's your take on these? |
|
We dont use stored procedures at work, but all other database changes like tables, triggers etc. are committed to git and deployed using github actions. There's no need to run the sql manually