Bug #50401 | Document bug 33000 in Manual | ||
---|---|---|---|
Submitted: | 18 Jan 2010 1:25 | Modified: | 18 May 2010 19:46 |
Reporter: | Leandro Morgado | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.0/5.1 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[18 Jan 2010 1:25]
Leandro Morgado
[18 May 2010 19:46]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Added to restrictions section: The trigger cache does not detect when metadata of the underlying objects has changed. If a trigger uses a table and the table has changed since the trigger was loaded into the cache, the trigger operates using the outdated metadata.
[13 Apr 2014 12:50]
MySQL Verification Team
do these warnings still need to be documented in 5.6 and 5.7 section?
[16 Apr 2014 7:03]
MySQL Verification Team
One instance of the bug still hits 5.6, 5.7. Bug 18596756 - FAILED PREPARING OF TRIGGER ON TRUNCATED TABLES CAUSE ERROR 1054