Description:
Test 'sp' contains a test for bug#7743.
On most platforms, this test fails with these symptoms:
/mysqldev/mysqldev/aix43/test/mysql-classic-5.0.3-alpha-ibm-aix4.3.3.0-powerpc/bin/mysqltest: At line 2597: Warning count is 1 but didn't get any warnings
/mysqldev/mysqldev/aix43/test/mysql-classic-5.0.3-alpha-ibm-aix4.3.3.0-powerpc/bin/mysqltest: At line 2989: Result length mismatch
-------------------------------------------------------
*** r/sp.result Sat Feb 19 03:33:23 2005
--- r/sp.reject Sat Feb 19 06:23:07 2005
***************
*** 2119,2124 ****
--- 2119,2126 ----
call bug7743("OneWord")|
var
NULL
+ Warnings:
+ Warning 1329 No data to FETCH
call bug7743("anotherword")|
var
2
***************
*** 2125,2130 ****
--- 2127,2134 ----
call bug7743("AnotherWord")|
var
NULL
+ Warnings:
+ Warning 1329 No data to FETCH
drop procedure bug7743|
drop table t4|
delete from t3|
-------------------------------------------------------
The effect seems to be independent of the product (standard, max, classic).
However, not all differences occur on all platforms, and some even pass the test.
A detailed list can be provided.
The most recent changesets in this build:
ChangeSet
1.1862 05/02/18 17:46:30 pem@mysql.com +1 -0
Merge mysql.com:/usr/local/bk/mysql-5.0
into mysql.com:/home/pem/work/mysql-5.0
ChangeSet
1.1856.1.1 05/02/18 17:39:32 pem@mysql.comhem.se +3 -0
Fixed...
BUG#6642: Stored procedure crash if expression with set function
BUG#7013: Stored procedure crash if group by ... with rollup
BUG#7743: 'Lost connection to MySQL server during query' on Stored Procedure
BUG#7992: SELECT .. INTO variable .. within Stored Procedure crashes
the server
BUG#8116: calling simple stored procedure twice in a row results
in server crash
Rolling back the item change list after each substatement in a procedure
fixed the failing assert().
How to repeat:
Try to build ...
