I fucked the database and had to restore from backup, sorry!

Hey guys,

So I had to roll back the entire database to the state it was at 00:00 UTC on the 24th (earlier this morning). This was because I put a query into the DB without looking properly and overwrote the imagic field of every single entry ever made to '0'.
Really sorry to those of you who put in contributions today but I'm afraid they're lost forever and would need re-doing if you're still keen. Also means that any items that had been processed by me today are now unprocessed. Same goes for any forum posts , signups, or pretty much any interaction at all. Personally lost about 6 hours of work today, I think Storm had hundreds of contribs approved...

Would be nice if phpMyAdmin warned me that I was about to overwrite 4900+ rows of data, or had an undo button. But nope, hard reality is that what's queried stays queried.

Again, apologies for the inconvenience guys.

Krythic wrote: 3 years ago

I was wondering what just happened to my two table posts. I'm sad now. =(

Really sorry dude omg.. I'd salvage them if I could but they're like, gone gone.

Storm <3

I've updated the automatic DB backup cron to once every 6 hours now just in case this happens again.

walker34j wrote: 3 years ago

@Teebling I recommend taking a bit of extra time to wrap any sql statement like that in a transaction with a rollback. I've been burned once too many times to write ANY statement on the live database without first putting it in a begin; rollback; transaction.

I usually do the following:

Code: Select all

begin;

-- UPDATE or DELETE statement here
-- SELECT statement here that shows me the change I intended to make

rollback;

Once I'm happy with the change, I'll change the rollback; to a commit;.

Wow, thanks for this tip!