Bug #8614 | distinct sometimes ignored with group by "CONST" | ||
---|---|---|---|
Submitted: | 19 Feb 2005 0:53 | Modified: | 22 Jun 2005 2:29 |
Reporter: | Martin Friebe (Gold Quality Contributor) (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 4.1.10 | OS: | Any (*) |
Assigned to: | Igor Babaev | CPU Architecture: | Any |
[19 Feb 2005 0:53]
Martin Friebe
[16 Jun 2005 16:45]
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/26082
[16 Jun 2005 18:59]
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/26089
[17 Jun 2005 17:44]
Igor Babaev
ChangeSet 1.2297 05/06/16 09:45:41 igor@rurik.mysql.com +3 -0 group_by.result, group_by.test: Added a test case for bug #8614. sql_select.cc: Fixed bug #8614. SELECT DISTINCT ... GROUP BY 'const' must be equivalent to SELECT ... GROUP BY 'const'. The fix will appear in 4.1.13 and 5.0.8.
[22 Jun 2005 2:29]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: Documented bugfix in Change History for 4.1.13 and 5.0.8; marked bug Closed.