MySQL Bugs: #120041: Incorrect collation forcing and data type disappearance on Turkish OS

Bug #120041	Incorrect collation forcing and data type disappearance on Turkish OS
Submitted:	12 Mar 13:40
Reporter:	Salih Şahin	Email Updates:
Status:	Won't Fix	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.46	OS:	Windows (Turkish)
Assigned to:		CPU Architecture:	x86
Tags:	collation, Data type 'INT', EER Diagram

Description:
I am experiencing a persistent issue in MySQL Workbench while creating a schema in the EER Diagram view. Even though I manually select utf8mb4_general_ci as the charset/collation, the application automatically reverts or displays it as utf8mb4_0900_ai_ci.

Furthermore, when I define a column as INT (or any data type containing the letter "I") and click the "Apply" button, the data type field appears blank or disappears. This issue specifically occurs with data types such as INT, DATETIME, DECIMAL, and TINYINT.

I suspect this is related to the Windows operating system language being set to Turkish. The "Turkish I" character mapping (i/İ and ı/I) seems to prevent the application from correctly parsing these data types during the SQL generation or application process.

How to repeat:
Errors can occur when creating a new schema and table or using an EER diagram on a Turkish Windows operating system.

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.