Bug #2329 Crash if insert with variable name in stored procedure
Submitted: 8 Jan 2004 17:16 Modified: 14 Jan 2004 3:55
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.0-alpha-debug OS:Linux (SuSE 8.2)
Assigned to: Bugs System CPU Architecture:Any

[8 Jan 2004 17:16] Peter Gulutzan
Description:
If I use "INSERT ... (variable_name) ..." or REPLACE ..... SET variable_name = value" , I 
get a crash.  
 
Possibly this is related to bug#2272, which is now closed. 
 

How to repeat:
mysql> create table t (s1 int)// 
Query OK, 0 rows affected (0.32 sec) 
 
mysql> create procedure pt () begin declare v int; insert into t (v) values (5); end// 
Query OK, 0 rows affected, 1 warning (0.00 sec) 
 
mysql> call pt()// 
ERROR 2013 (HY000): Lost connection to MySQL server during query 
 
.... restart mysqld ... 
 
mysql> create procedure pv () begin declare v int; replace t set v = 5; end// 
Query OK, 0 rows affected, 1 warning (0.01 sec) 
 
mysql> call pv()// 
ERROR 2013 (HY000): Lost connection to MySQL server during query
[9 Jan 2004 8:00] Dean Ellis
This also occurs even if the variable name is actually a column in the table.
[14 Jan 2004 3:55] 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