2012-07-31, 01:48 PM
I have encountered an issue similar to this one:
http://community.mybb.com/post-687845.html
This is triggered by phpBB3 user names which are similar, but have different letter variations, for instance: "René" and "Rene".
My instance of phpBB uses utf8_bin as collation:
While MyBB uses utf8 as collation:
So I did the following change before triggering the merge :
The error doesn't occur anymore, and the import is then successful, but I am wondering:
Thanks !
Olivier
http://community.mybb.com/post-687845.html
This is triggered by phpBB3 user names which are similar, but have different letter variations, for instance: "René" and "Rene".
My instance of phpBB uses utf8_bin as collation:
show create table phpbb3_users;
`username` varchar(255) collate utf8_bin NOT NULL default '',
While MyBB uses utf8 as collation:
show create table mybb_users;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `mybb_users` (
`uid` int(10) unsigned NOT NULL auto_increment,
`username` varchar(120) NOT NULL default '',
So I did the following change before triggering the merge :
diff -u mybb-0[12]*
--- mybb-01-after-install.dump 2012-07-31 13:49:45.000000000 +0200
+++ mybb-02-encoding.dump 2012-07-31 14:04:55.000000000 +0200
@@ -2084,7 +2084,7 @@
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `mybb_users` (
`uid` int(10) unsigned NOT NULL auto_increment,
- `username` varchar(120) NOT NULL default '',
+ `username` varchar(120) collate utf8_bin NOT NULL default '',
`password` varchar(120) NOT NULL default '',
`salt` varchar(10) NOT NULL default '',
`loginkey` varchar(50) NOT NULL default '',
The error doesn't occur anymore, and the import is then successful, but I am wondering:
- Is this specific to my case ?
- Will my solution have bad side effects in the long term ?
- Any recommendation for a clean solution ?
Thanks !
Olivier