Redundant database tables after upgrade Redundant database tables after upgrade
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

Redundant database tables after upgrade

Started by Bill Roberts, February 28, 2009, 02:47:10 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Bill Roberts

I just upgraded to 1.4.20 and it works!

Now I have what appears to be a duplicate set of tables in the database, one prefixed cpg14x and one prefixed cpg132.

Are they redundant and can I safely drop the cpg132 tables?

Nibbler

That means you didn't upgrade correctly. Check include/config.inc.php and see what prefix Coppermine is actually using.

Bill Roberts

// MySQL TABLE NAMES PREFIX
$CONFIG['TABLE_PREFIX'] =                'cpg132_';

Can I edit the file to correct it?

Or is it more complicated?

Nibbler

Don't change the file. That means you can drop the cpg14x tables. Check them first though to make sure they don't have anything you want.