Extending database using same or different table_prefix

  • Resolved trevorstokes

    (@trevortokes)


    8 years, 11 months ago

    I have extended the wp database. I maintain the content with a separate sub-system, but also feed data to the WordPress site using a plug in.
    I used a different table_prefix for my tables. Everything is working fine, but free backup plugins or utilities do not backup my tables. (Updraft, Softaculous.)
    I use constraints (referential integrity) and “hook” into the wp_users table.

    Is there any reason I could not use the same table prefix (“wp_”)for my tables?
    I did experiment on L.A.M.P. where I do my development and it seems OK. I named my tables “wp_gyc_…”.

    I’m concerned that WordPress might delete my tables or future additions could clash.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Maciek Palmowski

    (@palmiak)

    8 years, 11 months ago

    But you should use the same prefix – WP won’t delete extra tables – don’t worry.

    Also it’s logical that all tables used by single WP have the same prefix.

    Moderator bcworkz

    (@bcworkz)

    8 years, 11 months ago

    AFAIK WP will not ever delete tables it did not create unless it’s the same name as one it did create. There is always a chance of future clash, but selecting unusual table names would make that extremely unlikely. If you run pre-release builds on your dev site, you’ll learn of the clash well before the problem hits production sites. IMO, any reason for concern is extremely small.

    Thread Starter trevorstokes

    (@trevortokes)

    8 years, 11 months ago

    Great. That’s what I hoped. I can rename my live tables using phpMyAdmin.

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

The topic ‘Extending database using same or different table_prefix’ is closed to new replies.