On 10/12/2011 04:50 PM, Roman Muntyanu wrote:
Thanks Sergiu for your help. I'll go with the second approach.
Please let me know if that solves the problem, so that I can put a warning in the release notes.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Wednesday, October 12, 2011 21:44 PM To: XWiki Users Subject: Re: [xwiki-users] Upgrade to 3.2 minor issues
On 10/12/2011 06:02 AM, coldserenity wrote:
Could you upgrade the version of MySQL used? I can try to but that might take me couple of days since I'm not a MySQL guru
Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? I have attached the file http://xwiki.475771.n2.nabble.com/file/n6884313/XwikiDatabaseCollation sAndEngines.txt XwikiDatabaseCollationsAndEngines.txt with engines/collations/encodings information. All of tables are on UTF8 but it turns out that all tables of my XWiki use 'MyISAM' engine except for 'activitystream_events_params' which uses 'InnoDB'. I have a strong feeling that's not how it should have been. Can this issue be also related to changing the hibernate dialect from 'org.hibernate.dialect.MySQLDialect' to 'org.hibernate.dialect.MySQL5InnoDBDialect'?
Yes, and my main suspect is the fact that MySQL doesn't support linking two types of tables with a foreign key.
You can do two things:
1. Change the configuration back to MySQLDialect, drop the activitystream_events_params table, restart XWiki.
2. Change all the other tables to use the InnoDB engine, with a statement like this for each table:
alter table xwikircs ENGINE=InnoDB;
For the future, 2 is better.
-- Sergiu Dumitriu http://purl.org/net/sergiu/