Bug #22580 DROP TABLE in nested stored procedure causes strange dependency error
| Submitted: | 22 Sep 2006 3:47 | Modified: | 9 Mar 2007 3:21 |
|---|---|---|---|
| Reporter: | Lachlan Mulcahy | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
| Version: | 5.0.26-BK, 5.0.24a | OS: | Any (Any) |
| Assigned to: | Marc ALFF | CPU Architecture: | Any |
| Tags: | stored function | ||
[22 Sep 2006 3:47]
Lachlan Mulcahy
[22 Sep 2006 6:32]
Valeriy Kravchuk
Thank you for a problem report. Verified just as described, also with 5.0.26-BK on Linux.
[20 Oct 2006 8:31]
Konstantin Osipov
Marc, this is likely a dup of the prelocking bug you have.
[8 Jan 2007 22:38]
Marc ALFF
For reference, the related pre-locking bug is Bug#8407.
[7 Mar 2007 1:06]
Marc ALFF
This bug has been fixed with Bug#8407.
[7 Mar 2007 22:04]
Konstantin Osipov
Pushed into 5.0.38 and 5.1.17.
[9 Mar 2007 3:21]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.
If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at
http://dev.mysql.com/doc/en/installing-source.html
Documented bugfix in 5.0.38 and 5.1.17 changelogs.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 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.