Bug #4318 Stored Procedure packet error if HANDLER statement
Submitted: 29 Jun 2004 0:44 Modified: 29 Jul 2004 17:08
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.1-alpha-debug OS:Linux (SuSE 8.2)
Assigned to: Per-Erik Martin CPU Architecture:Any

[29 Jun 2004 0:44] Peter Gulutzan
Description:
A call to a stored procedure with a HANDLER statement causes "Packets out of order" in 
any following statement. 
   

How to repeat:
mysql> create table t (s1 int); 
Query OK, 0 rows affected (0.31 sec) 
 
mysql> handler t open; 
Query OK, 0 rows affected (0.00 sec) 
 
mysql> create procedure p () handler t read next; 
Query OK, 0 rows affected (0.00 sec) 
 
mysql> call p(); 
Empty set (0.00 sec) 
 
mysql> call p(); 
Packets out of order (Found: 5, expected 1) 
ERROR 2013 (HY000): Lost connection to MySQL server during query
[29 Jul 2004 17:08] Per-Erik Martin
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

The most urgent problem (packets out of order) is fixed, but it doesn't return results
from within stored procedures. For the moment it's a little unclear what would be
the expected behaviour when mixing handler calls outside and inside a procedure...