Bug #5274 | Stored procedure crash if length of CHAR variable too great | ||
---|---|---|---|
Submitted: | 28 Aug 2004 1:30 | Modified: | 6 Apr 2007 15:40 |
Reporter: | Peter Gulutzan | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.2-alpha-debug | OS: | Linux (SuSE 8.2) |
Assigned to: | Alexander Nozdrin | CPU Architecture: | Any |
[28 Aug 2004 1:30]
Peter Gulutzan
[28 Aug 2004 6:25]
MySQL Verification Team
Verified against latest BK source. Thank you for the bug report.
[10 Sep 2004 15:46]
Per-Erik Martin
After the latest merge with 4.1 it no longer crashes - instead it's returning NULL which isn't right either...
[20 Apr 2005 10:17]
Per-Erik Martin
This now "works", in that it's not crashing. Instead NULL is returned and a truncation warning is set. This is due to the limitation that "select" can't return an error. (See also the related BUG#9856)
[6 Apr 2007 15:40]
Alexander Nozdrin
It does not repeat anymore. Version: 5.0.40.
[12 Apr 2007 15:43]
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/commits/24394 ChangeSet@1.2438, 2007-04-12 19:42:45+04:00, anozdrin@ibm. +2 -0 Test case for BUG#5274: Stored procedure crash if length of CHAR variable too great.
[23 Apr 2007 7:29]
Bugs System
Pushed into 5.1.18-beta
[23 Apr 2007 7:30]
Bugs System
Pushed into 5.0.42