Bug #46988 Cross-pollination from one local db to another
Submitted: 29 Aug 2009 3:38 Modified: 29 Aug 2009 6:12
Reporter: Vicki Frei Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: Storage Engines Severity:S2 (Serious)
Version:5.0.51a OS:Microsoft Windows (win7 RC)
Assigned to: CPU Architecture:Any

[29 Aug 2009 3:38] Vicki Frei
I'm not positive this is a bug.  However....

I develop websites locally using xampp.  My xampp version is 1.7.1.  I was re-theming a WordPress site for a client.  I finished the changes, exported the database, zipped the files, and uploaded to the live site.  I exported the live database as backup (good thing, too!), and then dropped the tables and imported the local database.  I selected the new theme in the wordpress backend.  Opening the site was a shock.

The site was confusingly compounded of information that simply did NOT belong.  After a few minutes, I thought I realized where some of the information that was displaying came from.  I reversed the changes to the live site, then started digging in my local folders.

It took me several hours to figure out what happened.  Somehow, two databases "munged" together - while I was making local changes to the client db, some of the changes I was making were actually being saved to a test db with NO relationship to the client db at all.

The config file for the WordPress installation was correctly set up to allow access to the database locally.  There was no reference to the other database at all, and of course, if you're familiar with WordPress, there's really no way to access more than one database.

It took me another few hours to sort out the information from the databases and put it where it belonged.  This is the first time anything like this has occurred in over 5 years of using xampp, mysql, phpmyadmin, and wordpress - which is why I'm not sure it's a bug.... though I honestly have no idea how I could have accomplished this situation without "help".

How to repeat:
I don't know how you could repeat this.
[29 Aug 2009 6:12] MySQL Verification Team
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.