Bug #118566 MySQL Workbench ignoring collation_connection
Submitted: 30 Jun 16:42 Modified: 1 Jul 4:56
Reporter: Pat Doherty Email Updates:
Status: Analyzing Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.42 OS:Windows (Microsoft Windows 10 Enterprise)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: WBBugReporter

[30 Jun 16:42] Pat Doherty
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\pdherty\AppData\Roaming\MySQL\Workbench\log\wb.log]

When connecting to an Amazon Aurora MySQL or RDS MySQL database using Workbench, it appears to ignore the "connection_collation" parameter. I set this in my parameter group and when I connect with Workbench I get this for the results:

Variable_name,Value
collation_connection,utf8mb4_0900_ai_ci
collation_database,latin1_swedish_ci
collation_server,utf8mb4_0900_ai_ci

Connecting to the same database using DBeaver I see the proper results:
"Variable_name","Value"
collation_connection,utf8mb4_general_ci
collation_database,utf8mb4_0900_ai_ci
collation_server,utf8mb4_0900_ai_ci

How to repeat:
1. Create an RDS MySQL 8.x or Amazon Aurora 3.x instance
2. Create a custom parameter group with "collation_connection" set to a non-default value
3. Connect to the database using MySQL Workbench
4. Run a SHOW VARIABLES LIKE 'collation%';

Suggested fix:
Ensure Workbench reads the "collation_connection" variable when connecting.