Bug #69750 | mysql 5.6.7-rc gives incorrect result when using distinct with order by | ||
---|---|---|---|
Submitted: | 15 Jul 2013 16:24 | Modified: | 15 Jul 2013 17:37 |
Reporter: | Manu Agarwal | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.7-rc | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | distinct, order by |
[15 Jul 2013 16:24]
Manu Agarwal
[15 Jul 2013 16:47]
Hartmut Holzgraefe
Didn't test specifically against 5.6.7 as i don't have it installed right now, but i can't reproduce this in current 5.6.12 or in older 5.6.5 using following simple test: create table dat(id int primary key auto_increment, d date); insert intop dat set d='2013-07-08'; insert intop dat set d='2013-07-09'; insert intop dat set d='2013-07-10'; insert intop dat set d='2013-07-11'; insert intop dat set d='2013-07-12'; select d from dat order by d desc; select distinct d from dat order by d desc; Both selects return the same result set with the correct year 2013 ...
[15 Jul 2013 17:37]
MySQL Verification Team
Hello Manu, Thank you for the report. I can not repeat described behavior on latest MySQL version 5.6.12 and with dummy data. Additionally version 5.6.7-rc(2012-09-29, Release Candidate) is old and many bugs were fixed since. Please could you try with the latest version and inform us if you can repeat this with the reproducible data? We do not fix bugs that are not repeatable with current versions. Thanks, Umesh