[wp-trac] [WordPress Trac] #4780: $table_prefix should not be encoded in table_names.

[WordPress Trac]

#4780: $table_prefix should not be encoded in table_names.
----------------------------+------------------------
 Reporter:  docwhat         |       Owner:  anonymous
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:  invalid
 Keywords:                  |
----------------------------+------------------------
Changes (by Converting2wp):

 * cc: Converting2wp (added)


Comment:

 I ran into this problem recently [1]. I'm migrating an old site (that had
 "wp_" as the table prefix) to a new host and wanted to run a dev site as
 well as production off one database in the new environment. I wanted to
 import the old database, change its prefix to "dev_xxx_" and eventually
 build out a new set of tables with "prod_xxx_" as their prefix. (That's my
 answer to the question above, "Why would someone want to change a table
 prefix?", if an answer other than "implementing the recommended
 obfuscation sometime after install" is not sufficient.)

 Anyway, I found the following values

 table_prefix_usermeta.wp_dashboard_quick_press_last_post_id,
 table_prefix_options.wp_optimize

 that aren't in the above list. It appears that the second needs to have
 the column value changed, but perhaps the second doesn't? Are there other
 dependencies on the table prefix that would need to be changed along with
 the names of the columns?

 [I'll probably just take the path of creating new databases and using the
 default prefix.]

 [1] http://wordpress.org/support/topic/changing-table-prefix-current-
 state-of-the-art?replies=9

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/4780#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software