Bug #12922 | wrong results with GROUP BY on VIEW | ||
---|---|---|---|
Submitted: | 1 Sep 2005 1:57 | Modified: | 8 Sep 2005 19:15 |
Reporter: | Kolbe Kegel | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 5.0.11 | OS: | Linux (Linux) |
Assigned to: | Evgeny Potemkin | CPU Architecture: | Any |
[1 Sep 2005 1:57]
Kolbe Kegel
[6 Sep 2005 19:38]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/29393
[7 Sep 2005 17:49]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/29449
[7 Sep 2005 18:39]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/29454
[7 Sep 2005 20:44]
Evgeny Potemkin
Fields of view represented by Item_direct_view_ref. When complex expression such as if(sum()>...,...) is split to simpler parts refs was ignored. Beside this direct ref doesn't use it's result_field and thus can't store it's result in tmp table which is needed for sum() ... group. All this results in reported bug. Fixed in 5.0.13, cset 1.1957.4.1
[8 Sep 2005 19:15]
Paul DuBois
Noted in 5.0.13 changelog.