On 10/12/2011 04:01 AM, coldserenity wrote: Please report anything you still don't like with the search results. Adjusting the scoring mechanism isn't something that can be precisely done without real word experiments, so real feedback is much appreciated (and needed). Weird, it doesn't look like code problem, but more like a database one. (Google pointed me to http://bugs.mysql.com/bug.php?id=25596). Can you provide the full stacktrace for this + mysql version? To answer your question, the activitystream_events_params table isn't important yet, it's not used by default, so yes, you can ignore the error for the moment, although we'd like to fix it. -- Sergiu Dumitriu http://purl.org/net/sergiu/

On 10/12/2011 04:53 AM, coldserenity wrote: Hm, it's really weird. Could you upgrade the version of MySQL used? Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? -- Sergiu Dumitriu http://purl.org/net/sergiu/

On 10/12/2011 06:02 AM, coldserenity wrote: 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/

On 10/12/2011 04:50 PM, Roman Muntyanu wrote: Please let me know if that solves the problem, so that I can put a warning in the release notes. -- Sergiu Dumitriu http://purl.org/net/sergiu/

Hi Sergiu, I have updated my database engine to 'InnoDB'. I just took the query from previously attached file and by using Notepad++ and text replace created a set of alters to update engine. I ran those alters one-by-one. With a success :) ============================================== Some helpful queries and steps ============================================== 1. Backup current wiki mysqldump --user=xwiki --password=xwiki --default-character-set=utf8 xwiki_utf8 > dump.sql 2. Create new database CREATE DATABASE db_name xwiki_utf8_innodb CHARACTER SET=utf8 COLLATE=utf8_general_ci 3. Import data from backup into new database mysql --user=xwiki --password=xwiki --default-character-set=utf8 xwiki_utf8_innodb < dump.sql 4. Log-in to mysql mysql --user=xwiki --password=xwiki 5. Switch to newly created database use xwiki_utf8_innodb; 6. Get list of tables requiring update SELECT TABLE_SCHEMA, TABLE_NAME, ENGINE, COLLATION_NAME, CHARACTER_SET_NAME FROM information_schema.`TABLES` T, information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA WHERE CCSA.collation_name = T.table_collation AND T.table_schema = "xwiki_utf8_innodb"; 7. Capture the output from previous and replace '| xwiki_utf8_innodb |' -> 'ALTER TABLE' '| MyISAM | utf8_general_ci | utf8 |' -> 'ENGINE=InnoDB' 8. Run list of created alters from previous step one-by-one 9. Verify that all engines are updated. 10. Update your hibernate.cfg.xml to use new database 11. Restart Tomcat -- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p696… Sent from the XWiki- Users mailing list archive at Nabble.com.