Bug #51532 Query Browser result area empty
Submitted: 26 Feb 2010 2:10 Modified: 26 Mar 2010 4:19
Reporter: Bruce Norgan Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.17 OS:Windows (Vista Business)
Assigned to: CPU Architecture:Any
Tags: From GUI Tools 5.0

[26 Feb 2010 2:10] Bruce Norgan 
Description:
The same problem still exists that was in version r15 of MySQL Query Browser version r17 that I downloaded today from GUI Tools 5.0 (there was no choice for this in "category" above).  When a query is executed it reports how many rows were fetched and a display of alternating blue and white stripes is shown in the result area.  But there is no data presented there.  The number of striped rows corresponds to the number of rows fetched, and unless the connection had been validly made, no rows would have been found anyway.  So the bug is that there is no data displayed even though it says it found some.  In the last report on the same subject you said it worked okay for you so I assumed you were implying something was wrong with my system.  But the latest MySQL version and the other apps are working, so maybe the assumption that something is wrong with my computer wouldn't exactly be correct.

How to repeat:
Run a query, observe that records were fetched, and look to see if the result area is empty.  Perhaps its impossible for you to duplicate a test with exactly the same MS Vista Business OS and HP laptop that I have.  I have to assume that unless you try something different, your response will be the same as before.

Suggested fix:
Look at the code and see what would prevent valid results from being displayed.
[26 Feb 2010 4:19] Valeriy Kravchuk 
Please, give bug number or URL for the bug report for QB 1.2.15 that you refers to.
[27 Mar 2010 0:00] Bugs System 
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".