-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge system - issue importing from phpbb3 utf8-bin - duplicated entrie #209
Comments
That’s an interesting one. The duplicate check is done in the code I believe, and it perhaps doesn’t do that in a way that understand what’s going on. We’ll have to take a look, though the merge system at the minute is mostly unmaintained.
… On 19 Jun 2018, at 23:59, lordgittux ***@***.***> wrote:
Hi, I'm trying to use the merge but when importin users I have issue with names with special characters, let me show:
On the phpbb I have two users
jonatas and Jônatas, the encode is utf8_bin, but when mybb try to import, he considere jonatas and Jônatas the same user and because that issue a message of duplicated entry.
Have anyone faced this problem?
Tried a couple of configurations for encode on the merge but nothing worked.
To add more information, I changed the collation of the field username on mybb_users to utf8_bin, someone know if there is some type of problem if I let the field remain as this?
ALTER TABLE mybb_users CHANGE username username VARCHAR(120) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '';
Appears that I will be unable to migrate from phpbb3 due this encoding issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I think that is a issue with the used collation, I installed a fresh version of the mybb, I tried create both users to test, no sucess, because the collation it compares Jônatas with jonatas and take them as equal. After my conversion to utf8_bin the second user was created normally. |
I think this issue does not relate to SQL's collation but the character set. The mechanism of user duplicate checking is coded in the For @lordgittux 's problem,
@euantorano, yep here's the interesting point, looks like the duplicate check in base I opened #226, in which there's some discussion of the UTF-8 problem would potentially relate to the user duplicate check. Edited: typo. |
Hi, I'm trying to use the merge but when importin users I have issue with names with special characters, let me show:
On the phpbb I have two users
jonatas and Jônatas, the encode is utf8_bin, but when mybb try to import, he considere jonatas and Jônatas the same user and because that issue a message of duplicated entry.
Have anyone faced this problem?
Tried a couple of configurations for encode on the merge but nothing worked.
To add more information, I changed the collation of the field username on mybb_users to utf8_bin, someone know if there is some type of problem if I let the field remain as this?
ALTER TABLE
mybb_users
CHANGEusername
username
VARCHAR(120) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '';Appears that I will be unable to migrate from phpbb3 due this encoding issue.
The text was updated successfully, but these errors were encountered: