MySQL Bugs: #105646: Error parsing DDL when clicking editor icon on a view with accented characters

Bug #105646	Error parsing DDL when clicking editor icon on a view with accented characters
Submitted:	19 Nov 2021 18:22	Modified:	26 Feb 2023 17:38
Reporter:	Jean-Paul Goemaere	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	8.0.23, 8.0.24, 8.0.25, 8.0.26, 8.0.27, 8.0.28, 8.0.29,8.0.30, 8.0.31, 8.0.32, 8.0.33	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	accented, characters, DDL, error, parsing

Description:
Error parsing DDL when clicking the editor icon on a view with accented characters.
This is new with 8.0.23 and later. It was working correctly up to 8.0.22.

How to repeat:
In MySQL WorkBench, execute the following SQL to create a table and a view : 

CREATE TABLE `table-test` (
  `Numéro` int NOT NULL AUTO_INCREMENT,
  `Nom` varchar(100) NOT NULL,
  `Prénom` varchar(100) NOT NULL,
  PRIMARY KEY (`Numéro`)  ) ;

CREATE VIEW `view-test` AS 
  select  `table-test`.`Nom` AS `Nom`,`table-test`.`Prénom` AS `Prénom` 
  from `table-test` 
  order by `table-test`.`Nom`,`table-test`.`Prénom`;

Now, in the schema navigator, click on the view editor icon near the view.
You get "Error parsing DDL for `test`.`view-test`.
When you than click on the "View DDL" button, you can see that the back quotes (`), surrounding the column names have disappeared.  

This is new with 8.0.23 and later. It was working correctly up to 8.0.22.

reproducible up to current version 8.0.27

Thank you for the bug report.

I have the same error, fields with symbols also fail for example select `is_enabled?`,'user_no.' from table; I know it's not a good practice but some old companies have this kind of things in their data bases. Please give support for this again in the next version. Greetings!

Bug #108081 marked as duplicate of this one.

Hi, when can we expect this bug to be fixed? This is quite a critical bug that prevents our scripts from developing properly. Is it possible for special characters and accents to be added to the MySQL Workbench dictionary (so that they are accepted like other characters)?

Hi, when can we expect this bug to be fixed? This is very important to us as we are unable to modify the code when the DDL error occurs.

I have exactly the same problem with special characters and missing acutes. Do you have any solution for that?

Hi, do we have any update for this issue?

Issue still exists in MySQL Workbench 8.0.31 and it is very annoying and block work. Are you going to fix this issue? Could you please raise priority for this?

This problem is still not solved and blocks all upgrades behind 8.0.22. Increasing severuty to S1(Critical)

Bug #111121 marked as duplicate of this one.

Is there any update?

I still can see that error / issue when we are using accented characters or emoticons like "☹".

Is there any estimation when that issue will be solved?