Bug #12001 | C API - mysql_next_result() | ||
---|---|---|---|
Submitted: | 18 Jul 2005 9:33 | Modified: | 20 Jul 2005 15:19 |
Reporter: | Sela Lerer | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1 | OS: | Windows (Windows XP) |
Assigned to: | Georg Richter | CPU Architecture: | Any |
[18 Jul 2005 9:33]
Sela Lerer
[18 Jul 2005 9:38]
Sela Lerer
Work around: Just add "SELECT 1" or some other meaningless query to the bunch.
[18 Jul 2005 10:06]
Sela Lerer
Works fine without SELECT queries.
[18 Jul 2005 10:45]
Vasily Kishkin
Tested on Win 2003 , Microsoft Visual C 7.0. Test case is attached.
[18 Jul 2005 10:45]
Vasily Kishkin
Test case
Attachment: test.c (text/plain), 1.77 KiB.
[18 Jul 2005 12:43]
Sela Lerer
And Vasily? What happened? :-D
[18 Jul 2005 18:33]
Georg Richter
Only affects 4.1 - works ok with libmysql 5.0
[19 Jul 2005 6:19]
Sela Lerer
Happens to me with 5.0 library too (sending query to 4.1 server).
[19 Jul 2005 15:32]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/27305
[20 Jul 2005 11:37]
Georg Richter
patch pushed into 4.1.14
[20 Jul 2005 15:19]
Mike Hillyer
Documented in 4.1.14 changelog.