MySQL Bugs: #57399: Literal values not correctly quoted in INSERT commands

Bug #57399	Literal values not correctly quoted in INSERT commands
Submitted:	12 Oct 2010 9:04	Modified:	31 Dec 2010 15:09
Reporter:	Alexandros Georgiou	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.28 CE	OS:	Windows
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	insert, quotes, workbench

Description:
When I specify a literal value to be inserted into an ENUM column, the 

How to repeat:
say we have a table like:

create table foo (myenum enum('bar','baz'));

then with the editor i create a row with the word "bar" and the script becomes:

INSERT INTO FOO (myenum) VALUES(bar);

instead of 

INSERT INTO FOO (myenum) VALUES('bar');

...and the same happens with columns of type CHARACTER

Suggested fix:
add some quotes in the code that generates the INSERT commands in the script

Workbench currently only auto-quotes insert-values for text-type-columns. enum is not among the auto-quoted columns, by design - for datatype CHARACTER (which is actually an alias of the datatype CHAR) this is a missing.

Hi, can you please explain why does the workbench not quote enum values "by design"? My mysql setup requires the quotes or it doesn't accept the insert commands. Is there some option to switch either the workbench's policy regarding quotes or the database's? At the moment I am generating the script, editing it in a text editor to add quotes and dropping it in the mysql command line. Is there a better workaround?

thanks

related to bug #57545

fix confirmed in repository

An entry has been added to the 5.2.31 changelog:

Enum values entered into the Inserts Editor were not automatically quoted.