(no subject)

[geekchick]

Note to self:

Make sure when you construct that UPDATE statement next time that you remember to put in the "where primary_key=(the id)" part. Your update will do exactly what you ask it to do, not what you mean for it to do.

"Okay, all your meetings are belong to us in Colorado Springs. Always have been, always will be." *facepalm*

I am at least coherent enough to be working on my local development copy of the database. Thank $deity for small favors. See, this is what happens when I have to wake up in time to get to an appointment scheduled for an hour earlier than I normally have to be at work.

Comments

[tshuma]

Heh. This is exactly why I no longer allow myself to work while on Vicodin. "Press? Nope, we've only ever had one story written about us, ever. Honest! And it was written a lot." (I work at the Sun Microsystems Labs.)

Yay, backup and restoration policies.

[points.livejournal.com]

What if I set my browser to return:
id=1;delete * from foo; :)

[patgreene.livejournal.com]

"Okay, all your meetings are belong to us in Colorado Springs. Always have been, always will be."

I don't understand why this warrants a facepalm -- did you write it?

[geekchick]

Because not all the meetings are in Colorado Springs, or at least they weren't before I executed that update. =)

(Summary: I told the database to update these fields in that table with these values, but unfortunately left off the "but only where the record matches this particular id". If you do that, it update those fields in all of the records, thus making it look like all of our meetings for the last two years were in Colorado Springs. And that, ladies and gentlemen, is why you shouldn't develop using your live data. =) )

[gsh]

Not as bad as "rm * .o" which I did once on the deveopment code I had spent 18 months writing. The one on a raid 5 array, so it didn't need tape backup.