Bug #77549 I found a bug in mysql workbench (MW). which about MW's code editor.

• Submitted: 29 Jun 2015 19:13
• Modified: 18 Sep 2015 0:15
• Reporter: Anderson Bob
• Status: Closed
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 6.3.4.0 build 828
• OS: Windows (windows 7 x64)
• CPU Architecture: Any

[29 Jun 2015 19:13] Anderson Bob

Description:
The MW's editor alert the error when i used below codes line:
======>>  alter table orders modify productId int not null;
The error was pointed at "int" like this: "Syntax error: Unexpected 'int' (INT)".
But i still executed successfully it ?? Has someone'd met this?

How to repeat:
The MW's editor alert the error when i used below codes line:
======>>  alter table orders modify productId int not null;
The error was pointed at "int" like this: "Syntax error: Unexpected 'int' (INT)".
But i still executed successfully it ?? Has someone'd met this?

[29 Jun 2015 21:24] MySQL Verification Team

Thank you for the bug report. Please provide the output of show create table orders before to execute alter table orders modify productId int not null;
Thanks.

[30 Jul 2015 1:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

[31 Jul 2015 7:45] Bäuerle Jörg

I have exactly the same problem. A small test script would be:
##################
CREATE DATABASE TestDB;
USE TestDB;

CREATE TABLE `my_table` (
  `id` int NOT NULL,
  `foo` float NOT NULL,
  PRIMARY KEY (`id`)
);

ALTER TABLE `my_table` MODIFY COLUMN `foo` double DEFAULT '0';

##################

The editor in the MySQL Workbench shows the syntax error "unexpected 'double' (double)", but the script is executed correctly. In fact, when executed through the MySQL command line client the produced output is the following:

##################
mysql> source Bug_Report_Script.sql;
--------------
CREATE DATABASE TestDB
--------------

Query OK, 1 row affected (0.00 sec)

Database changed
--------------
CREATE TABLE `my_table` (
  `id` int NOT NULL,
  `foo` float NOT NULL,
  PRIMARY KEY (`id`)
)
--------------

Query OK, 0 rows affected (0.22 sec)

--------------
ALTER TABLE `my_table` MODIFY COLUMN `foo` double DEFAULT '0'
--------------

Query OK, 0 rows affected (0.47 sec)
Records: 0  Duplicates: 0  Warnings: 0

mysql> DESCRIBE my_table;
--------------
DESCRIBE my_table
--------------

+-------+---------+------+-----+---------+-------+
| Field | Type    | Null | Key | Default | Extra |
+-------+---------+------+-----+---------+-------+
| id    | int(11) | NO   | PRI | NULL    |       |
| foo   | double  | YES  |     | 0       |       |
+-------+---------+------+-----+---------+-------+
2 rows in set (0.00 sec)

mysql>
##################

This seems to indicate a bug in the syntax highlighting / parsing of the Workbench editor.

[2 Sep 2015 0:50] MySQL Verification Team

script executed

Attachment: bug_77549.png (image/png, text), 227.91 KiB.

[2 Sep 2015 0:51] MySQL Verification Team

@@ Bäuerle Jörg

Are you able to attach a screenshot of the error?. Thanks.

[2 Sep 2015 5:52] Bäuerle Jörg

Hi Miguel,

sure I can, but it looks exactly like the screenshot you have posted yourself.

Greetings,
Joerg

[2 Sep 2015 6:17] Bäuerle Jörg

Syntax error in editor highlighting

Attachment: Syntax_Error_Bug.png (image/png, text), 145.11 KiB.

[2 Sep 2015 10:03] MySQL Verification Team

Thank you for the feedback.

[18 Sep 2015 0:15] Philip Olson

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the changelog entry:

The SQL parser and grammar was updated; some queries would emit bogus
errors.

Thank you for the bug report.