Kill me now

[siercia]

So, I had the customer's data all installed on my laptop. And I'm tinkering with it, and life is good. Gonna pretty it before I arrive on site tomorrow, flawless victory for Jenn, right.

Except, as I'm tinkering, somehow I manage to delete the entirety of the users table from the database. I'm not sure how or why Query Analyzer thought my command was a good one for deleting EVERYBODY, but it sure did. Thank goodness I have a backup of the database here too, even if all my work this afternoon is down the tubes.

Sheesh.

Comments

[cogshiftingman.livejournal.com]

Can't you "roll back" what you did? I've never been in that situation, but doesn't SQLServer have rollback? But maybe you aren't using SQLServer ...

[cogshiftingman.livejournal.com]

Can't you "roll back" what you did? I've never been in that situation, but doesn't SQLServer have rollback? But maybe you aren't using SQLServer ...

Oh that was funny. I tried to post the comment above, and received this: [Error: Lost connection to MySQL server during query at /home/lj/cgi-bin/talklib.pl line 1376, line 19. @ w17]

Aren't databases fun?!

[siercia]

Even funnier is that I got both comments =)

Had I been a smart do-bee and actually USED the begin tran/commit tran/rollback tran commands, I would have been all set. But who ever thinks they're going to need THAT? Later in the evening, properly en-smartened, I WAS using that when I did the SAME DAMN THING with a different SQL Query. Always learning, that's me!

[siercia]

Even funnier is that I got both comments =)

Had I been a smart do-bee and actually USED the begin tran/commit tran/rollback tran commands, I would have been all set. But who ever thinks they're going to need THAT? Later in the evening, properly en-smartened, I WAS using that when I did the SAME DAMN THING with a different SQL Query. Always learning, that's me!

[cogshiftingman.livejournal.com]

Ah OK: now I've learned something too: the roll back feature is not "on" by default :-)