Bug #1046 | delete... order by crashes the server | ||
---|---|---|---|
Submitted: | 13 Aug 2003 18:19 | Modified: | 15 Aug 2003 5:43 |
Reporter: | Matthias Urlichs | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 4.1.0 | OS: | Linux (Linux 2.4.21) |
Assigned to: | CPU Architecture: | Any |
[13 Aug 2003 18:19]
Matthias Urlichs
[14 Aug 2003 5:47]
MySQL Verification Team
Thank you for your bug report. This issue has been fixed in the latest development tree for that product. You can find more information about accessing our development trees at http://www.mysql.com/doc/en/Installing_source_tree.html Actually, for 4.1.1 it is not available for download, but is fetchable from our BK public repository. I do not get crash, as this is fixed in 4.1.1. But I get a correct error message: { 150,"Foreign key constraint is incorrectly formed"},
[15 Aug 2003 3:21]
Matthias Urlichs
Please remove the FOREIGN KEY (`VERTRAG`) REFERENCES `vrtk` (`VTNR`) ON UPDATE CASCADE part, it refers to a table you don't have. (The error message, by the way, could be a whole lot better than "incorrectly formed".) If that shows that the problem is solved, good. Your message didn't really say whether you actually got to the last line of my SQL commands.
[15 Aug 2003 5:43]
MySQL Verification Team
I did ran it to the end and it worked like a charm. Not a bug.