Bug #6818 | undocumented change in alias behavior | ||
---|---|---|---|
Submitted: | 25 Nov 2004 1:42 | Modified: | 26 Nov 2004 7:35 |
Reporter: | Michael Stassen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 4.1.7 | OS: | |
Assigned to: | Dmitry Lenev | CPU Architecture: | Any |
[25 Nov 2004 1:42]
Michael Stassen
[25 Nov 2004 11:09]
Hartmut Holzgraefe
As far as i can tell it was sort of a bug that it worked in 4.0 at all as aliases are defined on the query and not on the table level. I'm changing this to Documentation category
[25 Nov 2004 17:37]
Michael Stassen
From the original post, it worked in 3.23 as well, which suggests that it has always worked until 4.1. I agree that it is strange that it worked, so treating it as a prior bug which is now fixed makes sense to me, but the change wasn't documented (as far as I can tell), hence the bug report. Also, if it is a bug to be fixed, note that it has not been fixed in 4.0.20. Is it fixed in the latest 4.0?
[26 Nov 2004 7:35]
Dmitry Lenev
Hi, Michael! This change appeared in MySQL 4.1.4. It was done as part of fix for bug #4302. The old behavior was non-standard and caused problems for some queries. (E.g.: SELECT id, calculate_price(price) as price FROM items ORDER BY items.price ) I have added note about this change to our release history http://dev.mysql.com/doc/mysql/en/News-4.1.4.html So far we don't have plans to fix it in 4.0 branch. Thank you spotting this and sorry about being so late with this note!!!