Bug #17704 | Triggers: MAX, Insert select with several rows, strange error | ||
---|---|---|---|
Submitted: | 24 Feb 2006 17:27 | Modified: | 17 Apr 2006 21:19 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[24 Feb 2006 17:27]
Matthias Leich
[24 Feb 2006 17:28]
Matthias Leich
testscript
Attachment: ml1104.test (application/test, text), 1.10 KiB.
[4 Mar 2006 13:41]
Konstantin Osipov
Stefan, I believe this is a documentation issue: there is an email to docs-requests with Subject: Re: Missing limitation of triggers/stored functions describing the exact problem. Please set to 'Not a bug' if this is fixed already. Matthias: a trigger can not access (not even read data) the table it's defined for.
[17 Apr 2006 21:19]
Dmitry Lenev
Hi, Matthias and Paul! I can't repeat behavior that you have described using the latest tree. With ltaest server error about table 't1' being marked as crashed is not emitted and code that you have provided works as expected. After closer look at your test case I am pretty sure that this bug is yet another manifestation of bug#17764 "trigger crashes myisam table" which is already fixed in 5.0.20. So I am marking this bug as duplicate.