[MDEV-4602] Error 1329 is reported even if it is handled Created: 2013-05-31 Updated: 2013-11-20 Resolved: 2013-11-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.31 |
| Fix Version/s: | 5.5.34 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Federico Razzoli | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | upstream | ||
| Description |
|
Create a trivial procedure with a cursor and a loop for that cursor. Handle the NOT FOUND event, or the 1329 error, or both.
Then run it:
As far as I understand this warning should not appear, because that warning is handled. |
| Comments |
| Comment by Elena Stepanova [ 2013-05-31 ] |
|
Hi Federico, This limitation/bug is documented in MySQL 5.5 manual (http://dev.mysql.com/doc/refman/5.5/en/condition-handling.html): "Before MySQL 5.6.3, if a statement that generates a warning or error causes a condition handler to be invoked, the handler may not clear the diagnostic area. This might lead to the appearance that the handler was not invoked. The following discussion demonstrates the issue and provides a workaround." I'm not quite sure it's worth backporting the fix from 5.6, but I'll get a second opinion. |
| Comment by Sergei Golubchik [ 2013-11-20 ] |
|
Fixed in 10.0 |