• theos244

    (@theos244)


    I have two databases: one of which I’m using on a dev server and the other is the live version that I have exported from the dev database and imported to the live one.

    I needed to go back and clear out the old dev database, and was going to import something else afterwards. I went and checked all the tables and did a DROP query, but for some reason, this dropped all the tables from both my dev database and the live database. Luckily, I had backups of everything, but could anyone tell me why this is happening?

    Here is my query, which is created when I do a ‘Check All’ tables and select ‘DROP’.

    DROP TABLE wp_commentmeta, wp_comments, wp_layerslider, wp_links, wp_options, wp_postmeta, wp_posts, wp_revslider_sliders, wp_revslider_slides, wp_slp_rep_query, wp_slp_rep_query_results, wp_store_locator, wp_terms, wp_term_relationships, wp_term_taxonomy, wp_usermeta, wp_users;

Viewing 3 replies - 1 through 3 (of 3 total)
  • Krishna

    (@1nexus)

    It looks highly unlikely as the databases are different at separate locations with separate database names. Is it that you unknowingly ran the query at both the databases?

    Thread Starter theos244

    (@theos244)

    I only ran the query once, from the menu in the dev database. I’ve been testing more and it isn’t specific to that query either. It’s like the databases are linked or something.

    Krishna

    (@1nexus)

    It’s like the databases are linked or something.

    No, it won’t happen as the names, locations, etc. are different. You can test it at another set of locations. Anyway, if it’s true, it’s strange.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘phpMyAdmin Drop Query Affecting Dev DB and Live DB’ is closed to new replies.