Bug #1250 | Server Crash on nested statement | ||
---|---|---|---|
Submitted: | 11 Sep 2003 9:11 | Modified: | 16 Jun 2004 12:54 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1.0 alpha | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[11 Sep 2003 9:11]
[ name withheld ]
[11 Sep 2003 13:24]
MySQL Verification Team
I tested your query with a server built from a BK 4.1 tree 2 days older: mysql> UPDATE at_person, at_personpalm SET KategorieNr=(select at_kategorie.id f rom -> at_kategorie where palmid=1), at_person.Name='bbbbb', Vorname='bbbbb', -> Addresse='bbbbb' WHERE at_person.Id=33 AND at_person.Id = -> at_personpalm.personnr; Query OK, 1 row affected (0.04 sec) Rows matched: 2 Changed: 1 Warnings: 0 Then this issue was already fixed for the next release.
[16 Jun 2004 12:52]
Oleksandr Byelkin
global ORDER BY do not belong to any table, it belong to result of union, result have only one field with such name, i.e. field is fully qualified
[16 Jun 2004 12:54]
Oleksandr Byelkin
sorry, it was comment for other bug record