MySQL Bugs: #23024: Blank Strings

Bug #23024	Blank Strings
Submitted:	5 Oct 2006 17:48	Modified:	19 Jan 2007 11:09
Reporter:	Oliver Thies	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.4	OS:	Windows (Windows 2000)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	Bad function on blank strings

Description:
The MysqlQuery Browser bad work on querys with blank lines.
Examples with line number.

1 blank line
2 update table_one where field = value;
3 select * from table_one where field = value;

How to repeat:
The MysqlQuery Browser bad work on querys with blank lines.
Examples with line number.

1 blank line
2 update table_one where field = value;
3 select * from table_one where field = value;

Suggested fix:
More tratament for input strings in query box.

Thank you for the bug report.

Bug: http://bugs.mysql.com/bug.php?id=23250 was marked as duplicate of
this one.

I'm not sure what to do with that report. Olivier, what is your actual problem? That you cannot execute an empty query? What exactly would you expect in such a scenario:

1  select * from foo;
2
3  select * from bar;

when the caret is on line 2? I'm sure you have already realized that the caret position decides which query is to be executed. So it is important that the caret is within the query to be executed. Since QB is a just a "machine" we need clear rules what is considered a query. The rule is: a query is the text between the first non-white-space after a delimiter or the editor start and the next delimiter (of course comments and string literals are not scanned for the delimiter) or the end of the editor text if there is no delimiter.

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".