MySQL Bugs: #42724: Query aborted

Bug #42724	Query aborted
Submitted:	10 Feb 2009 9:19	Modified:	10 Mar 2009 13:01
Reporter:	Ruediger Hahn	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.2.16	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	no resultset returned, query aborted

Description:
I think this is a duplicate of bug #38357. Unfortunately I wasn't able to reopen that bug.

When submitting my sql statement, I sometimes get the following messages in the status bar:
"No resultset returned." and right after that: "Query aborted." 
This happens about every second time executing exactly the same statement. When it works the statement returns about 11000 records with about 140 columns.

My environment:
* MySQL Query Browser 1.2.16.
*   on Windows XP SP3 with all MS patches applied.
* MySQL Server 5.0.70-r1
*   on Gentoo Linux with the latest updates

I don't get any errors in the server logs.
This behavior doesn't happen in the mysql.exe 5.1.31 client console application on Windows XP.
This behavior doesn't happen in the mysql 5.0.70 client console application on Linux (Gentoo).

Some additional information I just found out:
It seems that this error only happens when I fetch one column twice (in my special case the last), like this:
"SELECT `ColumnA`, `ColumnB`, `ColumnC`, `ColumnD`, `ColumnE`, `ColumnE` from `TableA`"
So far, I didn't check this out with other columns.

Ruediger

How to repeat:
Just execute the same statement within the Query Browser. From time to time there will be the behavior described above.

I just had the problem that I couldn't reproduce the behavior any more. What I've done in the meantime was installing a jdbc-connector to connect to the server with OpenOffice.org.

But I don't think that this has anything to do with the problem. Fortunately I could eventually reproduce the error by adding some more column names to the statement.

So it seems that there is a problem with the number of column names in a sql statement. As I already mentioned above the table contains about 140 columns, which all have to be fetched by name in my special case.

To verify this I just created a statement like
"SELECT ColumnA, ColumnA, ColumnA, ..., ColumnA from SomeTable" with about 140 "ColumnA"s and was able to reproduce the error.

Hope this helps.

Ruediger

Thank you for the bug report. I couldn't repeat with a very large table with more than 600 columns (a table I was using try to repeat another bug report). Maybe I am missing something here, could you please provide the dump file of the table which allows to repeat the issue and your my.cnf file?. Thanks in advance.

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