| 5 | | We are talking about a option in the options table that is the only option ever that uses the database prefix (and multisite_id) in a table that is already using the prefix (and in case of a multisite also the multisite_id) in the tables name. |
| | 5 | Moreover the by you suggested replace is only for the main table as that is the only one without a multisite_id in the table names. All others have NEWPREFIX_MULTISITE_ID_usermeta |
| | 6 | |
| | 7 | UPDATE `newprefix_usermeta` SET `meta_key` = REPLACE( `meta_key` , 'oldprefix_', 'newprefix_' ); |
| | 8 | |
| | 9 | |
| | 10 | In case you have a big multisite you have to run this per usermeta ... that is a lot of fun. |
| | 11 | |
| | 12 | But here we are talking about a option in the options table that is the only option ever that uses the database prefix (and multisite_id) in a table that is already using the prefix (and in case of a multisite also the multisite_id) in the tables name. |