Here’s the thing

biorhythmist:

Let’s say I have a tumblr draft that I’ve spent a little time on. ;)

And let’s say I’m finally happy with this draft, what with it having all the proper emoticons and hyperbole, so I decide to publish it. :)

And then let’s say that An Error Has Occurred when I try to publish this draft. I get that. Shit happens from time to time when you are trying to maintain a live blogging platform with hundreds of thousands of users. No biggie. :/

But wouldn’t it be nice if tumblr didn’t lose the whole draft so that it shows up neither on the dashboard nor in my drafts? Like, say, oh, I don’t know, waiting for the draft to successfully publish before deleting it from drafts? :(

Twice? >:(

Mother pusbucket. :-S

Ladies. (.)(.)

There is a thing in database lingo called a transaction. Basically, it’s a group of related commands (subtract X dollars from account A; add X dollars to account B) of which it is absolutely guaranteed that either all will complete (payment) or none will (no payment), in which case the data “rolls back” to where it was before. This prevents an error in the middle of the sequence from causing an inconsistency (disappearing money; creditor lawsuit; FDIC investigation; loss of banking charter).

Pretty much all modern databases of any sophistication support transactions, and they’re super easy to use if, well, if you know what you’re doing.

I don’t know why I’m bringing this up now. Guess I just thought it was interesting.