Bug #53840 order by desc is not working after 99,999 records.
Submitted: 20 May 2010 8:29 Modified: 25 Apr 2011 19:49
Reporter: asma khanam Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: DDL Severity:S2 (Serious)
Version:5.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: select tag

[20 May 2010 8:29] asma khanam 
Description:
I am using a select command with order by desc. but after reaching 1 lac records order by desc in not working. till 99,999 records are displayed in descending order. but after that not in descending order.

How to repeat:
select t5._rowid from tagsentry t1,tagsassets_tagsentries t2,tagsasset t3,journalarticleresource t4,journalarticle t5 where (t1.entryid=t2.entryid) and (t2.assetid=t3.assetid) and (t3.classpk=t4.resourceprimkey) and (t4.articleid=t5.articleid) and t1.name='tv5money-spotlight'   order by t5.articleid desc limit 5;

when articleid's are more than 99,999 articles are getting displayed in descending order from 1 lac
[20 May 2010 8:33] asma khanam 
order by desc is not working after 99,999 records.

select t5._rowid from tagsentry t1,tagsassets_tagsentries t2,tagsasset t3,journalarticleresource t4,journalarticle t5 where (t1.entryid=t2.entryid) and (t2.assetid=t3.assetid) and (t3.classpk=t4.resourceprimkey) and (t4.articleid=t5.articleid) and t1.name='tv5money-spotlight'   order by t5.articleid desc limit 5

when i run this query after 99,999 record records are not displayed in descending order.
[20 May 2010 8:40] Valeriy Kravchuk 
What exact version, 5.0.x, do you use? Can you upload a dump of tables used to check the query? We need a repeatable test case to be able to fix the bug.
[20 Jun 2010 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[25 Mar 2011 19:45] Rick James 
Is articleID INT or VARCHAR?
[25 Apr 2011 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".