Bug #18162 Breaks with tab characters
Submitted: 12 Mar 2006 4:28 Modified: 23 Nov 2006 10:33
Reporter: Gamigin Gamigin Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.20 OS:Windows (Windows XP)
Assigned to: Mike Lischke CPU Architecture:Any
Tags: Source Editors

[12 Mar 2006 4:28] Gamigin Gamigin
Description:
If I try this on the mysql schema (note the leading tab character which was pasted in from another text editor), I get an error. Removing the tab or using space characters works fine.

	SELECT * FROM db;

Once I realize the issue, I can work around this bug, but the error message is extremely misleading and it's easy to spend hours breaking down a large query into a smaller reproducable sample and identify the exact issue.

How to repeat:
Paste the following into Query Browser and run against the mysql schema. Make sure to copy/paste the leading tab character.

	SELECT * FROM db;
[13 Mar 2006 0:33] MySQL Verification Team
Thank you for the bug report.
[24 Apr 2006 23:12] MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=19303 was marked as
duplicate of this one.
[25 May 2006 17:19] Erica Moss
I just bumped into this problem.  I was unable to run a script that has always worked fine for me.  We should take a look at this because any tab anywhere seems to cause an error.  It is not at all uncommon to have table definition and insert statements broken up into multiple lines with tabs.  IE
CREATE TABLE users(
	fName VARCHAR(25) NOT NULL,
	lName VARCHAR(25) NOT NULL,
	DOB  DATE NOT NULL,
	uID INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY);

If you open a script with statements like this and try to execute it you get a very generic and innacurate error message:
ERROR 1064: you have an error in your SQL syntax.
[1 Nov 2006 17:59] Luis Antonio Castro Henriques
I think this have to be escalated in severity, or will never get fixed. 

For me, this is the single reason I not use this appplication.
[23 Nov 2006 10:33] Mike Lischke
Duplicate of bug #16441