Bug #113075 MySQL Workbench doesn't generate collation into sql
Submitted: 14 Nov 2023 8:41 Modified: 15 Nov 2023 10:56
Reporter: Hailin Hu Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:8.0.34 OS:MacOS
Assigned to: CPU Architecture:Any

[14 Nov 2023 8:41] Hailin Hu
Description:
MySQL Workbench ignores explicitly announcement of collation for schema.

MySQL 8.0 uses utf8mb4_0900_ai_ci as the default collation for utf8mb4.
We created our database since MySQL 5.7. Now we are required to explicitly declare our non-default collation utf8mb4_general_ci in the modeling.
We use the exported SQL in CI/CD. The lack of collation will cause "Illegal mix of collations" errors.

How to repeat:
1. Create a model

2. Set Character Set to utf8mb4, and set Collation to utf8mb4_general_ci (NOT THE "Default Collation")

3. Export SQL (Cmd+Shift+G)

4. Can only get SQL as the below, COLLATE is missing.
CREATE SCHEMA IF NOT EXISTS `test` DEFAULT CHARACTER SET utf8mb4 ;
[14 Nov 2023 8:42] Hailin Hu
explicitly specify the collation

Attachment: スクリーンショット 2023-11-14 17.28.46.png (image/png, text), 112.78 KiB.

[14 Nov 2023 8:42] Hailin Hu
set target to mysql 8.0

Attachment: スクリーンショット 2023-11-14 17.29.09.png (image/png, text), 228.56 KiB.

[15 Nov 2023 10:56] MySQL Verification Team
Hello Hailin Hu,

Thank you for the bug report.
Imho this is duplicate of Bug #74680, please see Bug #74680.

Regards,
Ashwini Patil