Bug #99209 Workbench does not correctly show collation for tables
Submitted: 8 Apr 2020 14:40 Modified: 9 Apr 2020 6:26
Reporter: Peter Fales Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.19 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[8 Apr 2020 14:40] Peter Fales
Description:
The workbench GUI is not correctly showing the Collation for tables using non-default character sets

How to repeat:
1) (optional) Create a new database 

2) Create a new table within the database 

3) Change the character set to latin1 (using the GUI schema editor)
The GUI shows that the character set is latin1 and the collation is latin1_bin. However, SHOW CREATE TABLE shows that the table really still using the default collation

4) Change the collation to latin1_general_cs (using the GUI schema editor)
The GUI still shows that the collation is latin1_bin.   However SHOW CREATE now shows the new collation:

mysql> show create table new_table;
+-----------+------------------------------------------------------------------------------------------------------------------------------+
| Table     | Create Table                                                                                                                 |
+-----------+------------------------------------------------------------------------------------------------------------------------------+
| new_table | CREATE TABLE `new_table` (
  `idnew_table` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_general_cs |
+-----------+------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.02 sec)

Suggested fix:
The GUI charset/collation should correctly reflect the character set and collation currently used in the table.
[9 Apr 2020 6:26] MySQL Verification Team
Hello Peter,

Thank you for the report and feedback.

regards,
Umesh