News for hackers. Stuff that matters.
Re:Databases Were Not Designed for This by Pxtl on Sunday April 26, 2026 @06:15PM (#47915279)
So what do you do for "okay, we need to run this script that we've decided is a necessary operation". Special account? Everything go through the build server? I've been looking for tooling for "I need to do a production operation but I want it to have proper interlocks and reviews".
Re:Databases Were Not Designed for This by tyzoid on Sunday April 26, 2026 @06:58PM (#47915690)
You can use something like flyway on top of your existing git/cicd stack. Write the query as a migration, have it reviewed using your git code review process, and merge to run the migration.
Re:Databases Were Not Designed for This by sgarland on Monday April 27, 2026 @12:34AM (#47917729)
If it’s an incident, it’s usually manually run after review, with an audience. If it isn’t, it’s run as a script that goes through normal PR review.
Re:Databases Were Not Designed for This by Pxtl on Monday April 27, 2026 @01:37PM (#47924691)
That's what I'm getting at - so in the end, somebody really does need to have access to a regular sysadmin account on the server, even if it's not their default login. I was hoping that there was an option that didn't involve that sort of workflow, or abusing migration tools (since this isn't exactly a migration).