migrating CPG mysql tables engine from MyISAM to InnoDB migrating CPG mysql tables engine from MyISAM to InnoDB
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

migrating CPG mysql tables engine from MyISAM to InnoDB

Started by blackmamba, August 09, 2006, 12:05:11 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

blackmamba

Hi all:)

I just changed the main mysql engine from MyISAM to InnoDB and I've run into some errors when altered some of the CPG tables from MyISAM to InnoDB.

tables:
QuoteALTER TABLE `cpg143_hit_stats` ENGINE = innodb
#1214 - The used table type doesn't support FULLTEXT indexes

ALTER TABLE `cpg143_pictures` ENGINE = innodb
#1214 - The used table type doesn't support FULLTEXT indexes

ALTER TABLE `cpg_searchmod_last` ENGINE = innodb
#1075 - Incorrect table definition; there can be only one auto column and it must be defined as a key

I have the latest XAMPP 1.53a running MySQL 5.0.21 on winXP and the queries were made with phpMyAdmin - 2.8.1
Is it the searchmod fault?

Nibbler

You are switching to a table type that does not support some of the features of MyISAM. If you really want to do that then you can drop the keys it complains about.

blackmamba

10x Nibbler,

I have dropped the FULLTEXT keys and it now works. I have now all the tables in InnoDB format.

I'm still not sure how it will affect the overall performance since I have noticed an 30% increase in the CPU levels and 200% in the average time for queries.

So it is now twice slower and 30% more CPU expenssive for now.
Next step, i guess: optimising InnoDB