Groan! The drop table command doesnâ€™t truly clear away tables from an existing WordPress database, so that I can import identically named tables to bring the database up to date at my blog's new virtual home.
To-be-imported data comes out of a dump in verson 4.0.24, while the destination database is 4.0.17 at least. So a version clash isn't the problem, is it? Iâ€™m hoping Iâ€™m just overlooking something obvious, so that thereâ€™ll be an easy fix.
When I do drop table commands, MySQL says I've succeeded. But then when I try an import again, I get an error message protesting that there is an identical table--usually wp_categories.
I've even deleted the WP-related database from the new server--and yet still see an error message re an unwanted ghost table.
What's going on? Is WP refreshing tables behind my back? Or is a cache at my new Web host doing something evil?
Just to anticipate questions, the new host apparently does not include a GUI-style MySQL admin tool.
I suppose I could try workarounds, but I'd rather get at the root of the problem--for the sake of safety and integrity of my database.
David Rothman | TeleRead.org | 703-370-6540
Blog (existing host): http://www.teleread.org/blog