Bug #77265 | Collation not being set correctly | ||
---|---|---|---|
Submitted: | 6 Jun 2015 8:42 | Modified: | 19 Jul 2018 9:01 |
Reporter: | Charles Loh | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.22 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | collation |
[6 Jun 2015 8:42]
Charles Loh
[10 Sep 2015 15:09]
MySQL Verification Team
Please provide the output where shows the different collation for both tables. Thanks.
[14 Sep 2015 1:19]
Charles Loh
SELECT TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME, COLLATION_NAME FROM INFORMATION_SCHEMA.COLUMNS where table_schema='aspidentitydb' TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME,COLLATION_NAME aspidentitydb,table111,UserId,utf8_general_ci aspidentitydb,table111,RoleId,utf8_general_ci aspidentitydb,table111,IdentityUser_Id,utf8_general_ci aspidentitydb,table222,UserId,utf8_unicode_ci aspidentitydb,table222,RoleId,utf8_unicode_ci aspidentitydb,table222,IdentityUser_Id,utf8_unicode_ci
[19 Jun 2018 9:01]
MySQL Verification Team
That issue happened still with newest release?. Thanks.
[20 Jul 2018 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".