Bug #98775 SQL Editor freezes on parsing a valid query
Submitted: 28 Feb 2020 11:02 Modified: 28 Feb 2020 11:15
Reporter: Dennis Logemann Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:8.0.19, 8.0.26 OS:Windows (Multiple)
Assigned to: CPU Architecture:Any
Tags: parser freeze

[28 Feb 2020 11:02] Dennis Logemann
Description:
The SQL query editor freezes on editing a valid query.

This behaviour is independent of the MySQL connection and the Windows version. I tested on two different MySQL Workbench installations with different Windows versions and different user environment. Changing the MySQL connection does not change the behaviour, the SQL editor is still freezing. This is why I think this is a parser bug.

The wb.log contains no information regarding the freeze.

How to repeat:
Just open any MySQL connection, open a new tab, copy/paste the following query. Now delete the substring "VIA" in the last line and try to replace it with "QDG". The SQL editor freezes while typing "QDG" (of course don't type the quotation marks).

This is the query:

SELECT * FROM zolan.tabNCTSKopfdaten where Mandant = 'zca' AND 
(
Bezeichnung = 'EDG.REG1395853' OR 
Bezeichnung = 'AESEDG.REG1395853' OR 
Bezeichnung = 'EDG.AESEDG.REG1395853'
OR
Bezeichnung = 'VAL.80302370' OR 
Bezeichnung = 'AESVAL.80302370' OR 
Bezeichnung = 'VAL.AESVAL.80302370'
OR
Bezeichnung = 'SPA.R2003460' OR 
Bezeichnung = 'AESSPA.R2003460' OR 
Bezeichnung = 'SPA.AESSPA.R2003460'
OR
Bezeichnung = 'VIA.169662' OR 
Bezeichnung = 'AESVIA.169662' OR 
Bezeichnung = 'VIA.AESVIA.169662'
OR
Bezeichnung = 'QDG.DA09068' OR 
Bezeichnung = 'AESQDG.DA09068' OR 
Bezeichnung = 'QDG.AESQDG.DA09068'
OR
Bezeichnung = 'QDG.DA9085/8831/P20036' OR 
Bezeichnung = 'AESQDG.DA9085/8831/P20036' OR 
Bezeichnung = 'VIA.AESQDG.DA9085/8831/P20036'
)
[28 Feb 2020 11:15] MySQL Verification Team
Hello Dennis,

Thank you for the report and feedback.
Verified as described on WIn10 with WB 8.0.19.

regards,
Umesh
[24 Sep 2021 13:26] MySQL Verification Team
Bug #105025 marked as duplicate of this one.