I just wanted to rename a table in the database.
As usual, selected the table and renamed in the [Operations] menu. But instead of renaming, phpMyAdmin created a sub-table under the original one. I don't know how that happened, but it did.

So I selected the parent(original) table and selected the DROP. My fault is I didn't read the warning message, as I was sure it will drop the table. Clicked OK and boom! Whole database gone!

Thankfully, it was not a live one.
It was a new project, and the database was empty. But I have to recreate the whole structure. 2 days of work just gone... :bawling:

Hm, I have never experienced this kind of issue. Going to test it on my phpmyadmin installation

You should have the table construction scripted by now.

I never leave QA without a means to automate from a standing start an entire table's definition, especially if you have customers or you make money from the data.

You can go a step further in setting up timed/command issued table exports _IN_ QA using the mySql admin command lines. I do this and I can readily on it (the backup) anytime.

I also SVN my dev scripts as to never lose the revisions.

And for extra measure, the SVN is backed up.

Time is money.

Message me if you'd like some help.

I just wanted to rename a table in the database.
As usual, selected the table and renamed in the [Operations] menu. But instead of renaming, phpMyAdmin created a sub-table under the original one. I don't know how that happened, but it did.

So I selected the parent(original) table and selected the DROP. My fault is I didn't read the warning message, as I was sure it will drop the table. Clicked OK and boom! Whole database gone!

Thankfully, it was not a live one.
It was a new project, and the database was empty. But I have to recreate the whole structure. 2 days of work just gone... :bawling:

well, it wasnt phpmyadmin that dropped the database, sorry to say that....