Bug #63609 | Query with GROUP by , ORDER BY and LIMIT return one row , not expected count | ||
---|---|---|---|
Submitted: | 5 Dec 2011 17:18 | Modified: | 12 Dec 2011 18:25 |
Reporter: | Rumen Palov | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
Version: | Distrib 5.5.17, for FreeBSD7.4 (amd64) | OS: | FreeBSD (not tested on other OS) |
Assigned to: | CPU Architecture: | Any | |
Tags: | GROUP, limit, order, SELECT |
[5 Dec 2011 17:18]
Rumen Palov
[5 Dec 2011 17:24]
Valeriy Kravchuk
Looks like a duplicate of bug #61399. Please, check (try to use IGNORE INDEX hint, for example, to prevent use of that multiple column index...)
[6 Dec 2011 14:29]
Valeriy Kravchuk
Had you tried to use IGNORE INDEX() hint or otherwise prevent use of that index? I wonder if this changes anything.
[6 Dec 2011 14:56]
Rumen Palov
In these cases query work correct: *) "number*1" in GROUP - changes the index to `dt` *) USE INDEX(dt) *) Do not use LIMIT - just get all result set
[6 Dec 2011 14:58]
Rumen Palov
Yes, if I prevent usage of multiple index number_dt it works correct.
[6 Dec 2011 15:12]
Valeriy Kravchuk
Do you agree that this is a duplicate of bug #61399 then?
[6 Dec 2011 15:25]
Rumen Palov
Yes It seems to have similliar like bug #61399 , but in bug 61399 aren't returned any rows in result set. In our case there are some rows with wrong values. In first case described by me, there are some strange resutls - not digits( what they must to be , but some strange bytes in place of them ) If you think that they are equal - OK , I just want to help with debuging.
[12 Dec 2011 18:25]
Sveta Smirnova
Thank you for the feedback. Closed as duplicate of bug #61399