Bug #50835 Error reporting broken in SQL editors
Submitted: 2 Feb 2010 14:08 Modified: 9 Feb 2010 14:19
Reporter: Mike Lischke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version: OS:MacOS
Assigned to: Sergei Tkachenko CPU Architecture:Any

[2 Feb 2010 14:08] Mike Lischke 
Description:
None of the SQL editors in the modelling section report errors anymore. That concerns SP, View, SQL Script and Triggers editors.

How to repeat:
Create a new model, create a new table and open it. Switch to the Triggers tab and start typing. No error indication appears as it was before.

Suggested fix:
n/a
[4 Feb 2010 17:31] Johannes Taxacher 
fix confirmed
[9 Feb 2010 14:19] Tony Bedford 
An entry has been added to the 5.2.16 changelog:

The SQL code editors used in the modeling functionality within MySQL Workbench, for example in the Triggers tab of the Table Editor, failed to identify and highlight SQL code errors.