Changes between Initial Version and Version 1 of Ticket #29943


Ignore:
Timestamp:
Nov 11, 2018, 7:29:05 AM (5 years ago)
Author:
Taha Jahangir
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29943 – Description

    initial v1  
    2424
    2525I treat this as a bug, because the default behavior of admin module is not sensible (and not documented), and will result in performance bug in normal setups , and it cannot be changed in a simple manner (without copying/monkey-patching of `ChangeList.get_ordering` method).
     26
     27A stackoverflow topic about this behavior:
     28https://stackoverflow.com/questions/32419190/django-admin-incorrectly-adds-order-by-into-query
     29
     30The issue (and commit) when this behavior is introduced (~7 years ago)
     31#17198 -- Ensured that a deterministic order is used across all database backends
     32
     33In reply to https://code.djangoproject.com/ticket/17198#comment:14 :
     34In our cases (a ~2M row table), the duration of  `count(*)` query is ~300ms, but viewing the 2000th page (`LIMIT 100 OFFSET 200000`) is 8s!
Back to Top