Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m having trouble with a liferay installation that is suddenly (without any code modifications) failing with “dulplicate id” errors. We’ve identified that the issue may be solved by changing the mysql engine to InnoDB.
I’m planning the change now, but i’m not sure what complications are likely in the process.
I’ve checked for full text indexes mentioned in this question
Converting table from MyISAM to INNODB
Are there any other likely problems I should
Andrew, there are lots of differences between MyISAM and InnoDB, the least of which is the fact that they are controlled by different configuration options in the MySQL conf. There is also the fact that InnoDB is ACID compliant unlike MyISAM. Also, backups cant be done with just copying MYI and MYD files anymore. Then there is the matter of different size requirements, different index types, and different performance characteristics between the two engines.
Even though I like InnoDB is most cases, may I ask what leads you to believe that a switch to InnoDB will solve your problem? and perhaps you should be seeking an alternate answer to THAT question instead of this one?