558
Someone has to stop him
(startrek.website)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Feb 2024
558 points (99.5% liked)
Funny: Home of the Haha
5539 readers
1073 users here now
Welcome to /c/funny, a place for all your humorous and amusing content.
Looking for mods! Send an application to Stamets!
Our Rules:
-
Keep it civil. We're all people here. Be respectful to one another.
-
No sexism, racism, homophobia, transphobia or any other flavor of bigotry. I should not need to explain this one.
-
Try not to repost anything posted within the past month. Beyond that, go for it. Not everyone is on every site all the time.
Other Communities:
-
/c/TenForward@lemmy.world - Star Trek chat, memes and shitposts
-
/c/Memes@lemmy.world - General memes
founded 1 year ago
MODERATORS
And this is why temporary fixes live in production databases for decades.
We had a similar issue with batch management, and the quick & dirty fix was to export the relevant db entries to .csv, run it through a parser, apply the necessary modifications, export to .sql with all new column labels, and then change the front-end to display the value of the new fields only.
Ran that through a cron-job every 5 minutes and done.
End users complained about the "nil" in the field initially right after inputting new data. The quick fix to the quick fix? Set a default value to "calculating, please stand by" instead of nil. They'd be frantically reloading, but never again blame IT.