MySQL Bugs: #38357: Queries will sometimes abruptly abort and erroneously yield no result set

Bug #38357	Queries will sometimes abruptly abort and erroneously yield no result set
Submitted:	24 Jul 2008 22:18	Modified:	25 Aug 2008 4:06
Reporter:	Daniel Katz	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.12 (5.0-r12)	OS:	Windows (XP Pro)
Assigned to:		CPU Architecture:	Any
Tags:	query aborted

Description:
Sometimes when making a query, the query browser will flash the result set and then clear the screen with a "query aborted" message.

The only way to make the query run after that is to remove one of the tables.

How to repeat:
I cannot reliably reproduce this problem until it is in the error state.  I can't send you a data dump and the query either due to the data being somewhat sensitive.

Perhaps a clue lies in 'explain'.

I've pasted it in the private comment section.

Thank you for a problem report. Please, check if there are some unusual messages in the error log of server at the moments when you have this problem.

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

Hello,

I am also having this problem and can reproduce it.
I am using 
* 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

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.

I don't get any errors in the server logs.
I cannot reproduce this error in a Windows mysql.exe 5.1.31 client console application.
I cannot reproduce this error in the mysql 5.0.70 client 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`"
I didn't check this out with other columns.

Ruediger