Plugin leaves orphan DB Tables

  • Frank Gomez

    (@frank6tg)


    6 years, 5 months ago

    This plugin works great but it would be nice if it didn’t leave behind extra database tables. Would love to hear if you are working on a solution

Viewing 5 replies - 1 through 5 (of 5 total)
  • Luke Cavanagh

    (@lukefiretoss)

    6 years, 3 months ago

    @frank6tg

    Which database tables are you referring to?

    Thread Starter Frank Gomez

    (@frank6tg)

    6 years, 3 months ago

    If a site uses a custom table prefix instead of wp_ the standard prefix wp_ tables are created by this plugin when doing a migration. The tables are essentially empty, but not necessary.

    Thread Starter Frank Gomez

    (@frank6tg)

    6 years, 3 months ago

    So “ALL OF THE Standard Tables” are created wp_users wp_posts wp_comments etc.

    Luke Cavanagh

    (@lukefiretoss)

    6 years, 3 months ago

    @frank6tg

    In that case all of the wp_ prefix database tables of the new install site can be deleted using phpMyAdmin if the site being migrated over is using a different database prefix. I would remove the wp_ prefix database tables after the migration is complete.

    • This reply was modified 6 years, 3 months ago by Luke Cavanagh. Reason: clarify wording
    Thread Starter Frank Gomez

    (@frank6tg)

    6 years, 3 months ago

    I totally understand and that is my current practice but I would hope that there would be a commitment to improve the product. It is not unheard of to change a database prefix.

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

The topic ‘Plugin leaves orphan DB Tables’ is closed to new replies.