MySQL Bugs: #24789: column names containing blanks are not escaped correctly

Bug #24789	column names containing blanks are not escaped correctly
Submitted:	4 Dec 2006 9:25	Modified:	8 Jan 2007 14:58
Reporter:	Klaus Lenssen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.6 beta	OS:	Windows (Windows XP SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
If I build a query using drag & drop and the colums names in the schema contain blanks, i.e. "Fiscal Year", then the query is not build correctly. E.g. dragging the colums "Product ID" and "Fiscal Year" onto the query build drop-zone results into:

SELECT * FROM `ibbi-raw` i, i.Fiscal Year
WHERE i.Product ID AND i.Fiscal Year;

instead of:

SELECT * FROM `ibbi-raw` i, i.Fiscal Year
WHERE i.`Product ID` AND i.`Fiscal Year`;

How to repeat:
Use any schema with colum names containing blanks.

Suggested fix:
Colum names should be qouted (escaped?) automatically if they contain blanks.

Thank you for a problem report. Please, try to repeat with a newer version, 1.2.6 beta (from GUI Tools 5.0r6), and inform about the results.

repeated the test with the new 1.2.6 beta from GUI Tools 5.0r6 with the same result. Quoting still does not work as expected.

Thank you for the bug report.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html