Bug #15177 | already reported & fixed bug still existent!! | ||
---|---|---|---|
Submitted: | 23 Nov 2005 9:23 | Modified: | 23 Nov 2005 17:19 |
Reporter: | Corin Langosch | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.16 | OS: | Linux (linux debian) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[23 Nov 2005 9:23]
Corin Langosch
[23 Nov 2005 17:19]
MySQL Verification Team
Please see: http://dev.mysql.com/doc/refman/5.0/en/news-5-0-12.html # Incompatible change: Beginning with MySQL 5.0.12, natural joins and joins with USING, including outer join variants, are processed according to the SQL:2003 standard. The changes include elimination of redundant output columns for NATURAL joins and joins specified with a USING clause and proper ordering of output columns. (Bug #6136, Bug #6276, Bug #6489, Bug #6495, Bug #6558, Bug #9067, Bug #9978, Bug #10428, Bug #10646, Bug #10972.) The precedence of the comma operator also now is lower compared to JOIN. (Bug #4789, Bug #12065, Bug #13551.) These changes make MySQL more compliant with standard SQL. However, they can result in different output columns for some joins. Also, some queries that appeared to work correctly prior to 5.0.12 must be rewritten to comply with the standard. For details about the scope of the changes and examples that show what query rewrites are necessary, see Section 13.2.7.1, “JOIN Syntax”. http://dev.mysql.com/doc/refman/5.0/en/join.html