| Bug #21236 | sql mode set NULL for SQL SECURITY DEFINER procedures | ||
|---|---|---|---|
| Submitted: | 22 Jul 2006 23:15 | Modified: | 25 Aug 2006 16:13 |
| Reporter: | Erica Moss | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
| Version: | 5.0.25 -log | OS: | Linux (Fedora core 5) |
| Assigned to: | CPU Architecture: | Any | |
[24 Jul 2006 5:14]
Erica Moss
I have made some errors in this report.
Description: In the current dev build we are returning NULL when SHOW CREATE PROCEDURE is called for a procedure with a mode==DEFINER. In prior builds we returned no value at all. Although DEFINER is the default value, it would be more tidy and uniform if the statement returned that value rather than nothing as this could lead the unititiated to believe that the value simply isn't set. How to repeat: create database fooDB; use fooDB; CREATE PROCEDURE proc() SQL SECURITY DEFINER SELECT VERSION(); SHOW CREATE PROCEDURE fooDB.proc; DROP PROCEDURE proc; DROP DATABASE fooDB;