Data at Your Fingertips: Explore Our New Reporting and Statistical Capabilities By Ryan Ashbrook Tuesday at 01:29 PM
paul banks Posted January 24, 2015 Share Posted January 24, 2015 Step 1Some or all of the tables or columns in your database are not using a utf8 collation (ipb3backup_vars is latin1_swedish_ci). You must convert your database to UTF-8 in order to continue Step 2You have 338 table(s) in this database that are not UTF-8. You must convert these tables to UTF-8 before you can proceed with the upgrade. Step 3 Try starting Converter every time says: Error: COLLATION 'utf8_unicode_ci' is not valid for CHARACTER SET 'utf8mb4' File: /system/Db/Db.php Line: 186 I do not know more, can anybody help me? Link to comment Share on other sites More sharing options...
paul banks Posted January 26, 2015 Author Share Posted January 26, 2015 hello anybody help me Link to comment Share on other sites More sharing options...
bfarber Posted January 26, 2015 Share Posted January 26, 2015 This is a bug we noticed in the converter that should be fixed in the next release. Link to comment Share on other sites More sharing options...
TheSonic Posted January 26, 2015 Share Posted January 26, 2015 @bfarber Is this a bug in the UTF8-Convert or UTF8mb4? Paul banks is running MySQL 5.1, see http://www.ips-community.de/index.php?/topic/47-upgrade-von-347-auf-40/&do=findComment&comment=389This version does not support utf8mb4. Link to comment Share on other sites More sharing options...
bfarber Posted January 27, 2015 Share Posted January 27, 2015 He has a utf8mb4 table in his database, but chose utf8 when he converted - the software did not correctly account for this and tried to fix a utf8mb4 collation to utf8_unicode_ci on a utf8mb4 character set table which isn't allowed. It's a bug - we have seen it ourselves recently and fixed it for the next release. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.