1313
Whoops (thumbsnap.com)
you are viewing a single comment's thread
view the rest of the comments
[-] Rhinoshock@lemmy.world 29 points 1 year ago

In T-SQL:

BEGIN TRANSACTION

{query to update/delete records}

(If the query returned the expected amount of affected rows)

COMMIT TRANSACTION

(If the query did not return the expected amount of affected rows)

ROLLBACK TRANSACTION

Note: I’ve been told before that this will lock the affected table(s) until the changes made are committed or rolled back, but after looking it up it looks like it depends on a lot of minor details. Just be careful if you use it in production.

[-] jaybone@lemmy.world 7 points 1 year ago

Lol why did I have to scroll so far to see ROLLBACK

[-] rwhitisissle@lemmy.ml 3 points 1 year ago

Because this is c/programmerhumor and the OP hasn't covered ROLLBACK yet in his sophomore DB class.

[-] tweeks@feddit.nl 4 points 1 year ago

If for example a client application is (accidentally) firing doubled requests to your API, you might get deadlocks in this case. Which is not bad per se, as you don't want to conform to that behaviour. But it might also happen if you have two client applications with updates to the same resource (patching different fields for example), in that case you're blocking one party so a retry mechanism in the client or server side might be a solution.

Just something we noticed a while ago when using transactions.

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

Programmer Humor

32549 readers
506 users here now

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

Rules:

founded 5 years ago
MODERATORS