Bug #18498 SQLWARNING handler catches non-01 SQLSTATE conditions

Submitted:	24 Mar 2006 19:55	Modified:	11 Jul 2006 15:47
Reporter:	Ron Burk	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S3 (Non-critical)
Version:	mysql-standard-5.0.18	OS:	Linux (linux-686)
Assigned to:		CPU Architecture:	Any

Description:
The documentation claims:

SQLWARNING is shorthand for all SQLSTATE codes that begin with 01.

However, a handler for SQLWARNING will catch a MySql error of 1263, whose SQLSTATE code is 22004.

How to repeat:
Evoke a 1263 error in a stored function that has a handler for SQLWARNING. The handler will catch the error.

Suggested fix:
Either the code's wrong, or the documentation is. :-)

Thank you for a problem report. Please, send a complete test case (entire SP or function), and check it with a newer version, 5.0.19.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Possibly a duplicate of bug#9857

Check on a newever version, 5.0.22. Please, send a complete test case that demonstraits the wrong behaviour, if you can repeat it on 5.0.22.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.