FishEye 2.5 : Problems with very long comments and MySQL migration
This page last changed on Apr 12, 2010 by edawson.
Issue SymptomsThere is a known issue with FishEye 2.0.x and very long comments when migrating your database to MySQL Enterprise Server. In some circumstances, this might result in truncation of very long comments, causing data loss. Depending on your configuration, you may see an error message like this while migrating to MySQL Enterprise Server, causing the migration to fail: 2009-07-16 16:56:12,390 ERROR [ThreadPool1] fisheye.app com.cenqua.crucible.actions.admin.database.DBEditHelper-doGet - Database migration failed: java.sql.BatchUpdateException: Data truncation: Data too long for column 'cru_message' at row 1 java.sql.BatchUpdateException: Data truncation: Data too long for column 'cru_message' at row 1
For more information, see the JIRA issue. WorkaroundIf your data contains very long comments or review descriptions (longer than 21,845 multibyte unicode characters), consider avoiding use of MySQL Enterprise Server until this issue is resolved fully. Alternatively, use PostgreSQL or the default (built-in) HSQLDB database. The FishEye developers are actively working on a solution to this problem and it will be addressed in an upcoming FishEye point release. Requesting SupportIf you require assistance in resolving the problem, please raise a support request under the FishEye project. |
![]() |
Document generated by Confluence on Apr 03, 2011 23:09 |