MySQL Bugs: #56833: SQL sript obtained using MySQL GUI Tools is miss-interpreted in MySQL Workbench

Bug #56833	SQL sript obtained using MySQL GUI Tools is miss-interpreted in MySQL Workbench
Submitted:	17 Sep 2010 1:50	Modified:	11 Nov 2010 15:56
Reporter:	Francisco Henkel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.27 revision 6485	OS:	Any (Windows XP, Mac OS X)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Using MySQL GUI tools, I have exported a schema.
When I Try to run it usin MySQL workbench, I see that SQL editor "looses" a word in a line and the result is that from that Line to the end, the sintax are incorrect and the script ends at that line; the SQL parser modifies in a Insert sentence the name of a column, and this make the rest of the script invalid (after that line, the parser, do not find the end of the nine, and so the rest is invalid). I'll atach the script 
It still works fine using GUI tools.

How to repeat:
I'll send the script; just open the script and observe the line 423.

Indeed, file can be exported without errors using mysql command line client:

macbook-pro:5.5 openxs$ bin/mysql -uroot test < ~/Downloads/PacoBackupDEMO.sql 
macbook-pro:5.5 openxs$ echo $?
0

but gives weird error message about non-existing table (on line 423) when executing the same script from SQL Editor. This is a bug.

Fixed already in release.

fixed in current release (5.2.29)

An entry has been added to the 5.2.29 changelog:

A script that could successfully be executed on the MySQL Server, failed to execute in the MySQL Workbench SQL Editor.