Bug #23963 | Crash on queries that return 0 rows | ||
---|---|---|---|
Submitted: | 3 Nov 2006 20:50 | Modified: | 24 Nov 2006 7:54 |
Reporter: | Michael Yudlson | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S1 (Critical) |
Version: | 1.2.5beta | OS: | MacOS (Mac OS X 10.4.8) |
Assigned to: | CPU Architecture: | Any |
[3 Nov 2006 20:50]
Michael Yudlson
[8 Nov 2006 17:32]
Jesper Birkestrøm
Happens on MacBooks to... really annoying.
[20 Nov 2006 13:57]
Jeff H
Ditto on PPC 10.4.8
[20 Nov 2006 13:59]
Jeff H
Same result with Perl DBD::mysql driver.
[22 Nov 2006 0:40]
Tim Rowe
I can also confirm that this bug occurs on any query which returns no result rows. Identical hardware to the first post (C2D MBP, 2GB), running against MySQL5.0.17 and 5.0.21. Have not tested this against MySQL4.1 or earlier. It is extremely annoying :(
[24 Nov 2006 7:54]
Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Same as bug #23915