this post was submitted on 06 Nov 2023
1318 points (98.7% liked)

Programmer Humor

32601 readers
312 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] fushuan@lemm.ee 23 points 1 year ago (2 children)
[–] Blackmist 20 points 1 year ago (2 children)

I don't understand environments that don't wrap things in transactions by default.

Especially since an update or delete without a where clause is considered valid.

[–] finestnothing@lemmy.world 9 points 1 year ago* (last edited 1 year ago)

I'm a data engineer that occasionally has to work in sql server, I use dbeaver and have our prod servers default to auto-wrap in transactions and I have to push a button and confirm I know it's prod before it commits changes there, it's great and has saved me when I accidentally had a script switch servers. For the sandbox server I don't have that on because the changes there don't matter except for testing, and we can always remake the thing from scratch in a few hours. I haven't had an oppsie yet and I hope to keep that streak

[–] Ultraviolet@lemmy.world 3 points 1 year ago

SQL Server technically does behind the scenes, but automatically commits, which kind of defeats the purpose.

No transaction to rollback