#8408: add a new meta option: don't do count(*) in admin
---------------------------------------------+------------------------------
          Reporter:  lidaobing               |         Owner:  nobody  
            Status:  new                     |     Milestone:  post-1.0
         Component:  Admin interface         |       Version:  0.96    
        Resolution:                          |      Keywords:          
             Stage:  Design decision needed  |     Has_patch:  0       
        Needs_docs:  0                       |   Needs_tests:  0       
Needs_better_patch:  0                       |  
---------------------------------------------+------------------------------
Changes (by mtredinnick):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * milestone:  => post-1.0

Comment:

 I can't see that this is likely to happen. Firstly, it would be an admin
 option, not a meta option. Secondly, even with tens of thousands of rows
 in a test table here, the count takes far less than a second, so compared
 to the time for collecting the display data, rendering it and returning
 the page, it isn't that large a time slice.

 How many rows are in this table you are seeing the problem with?

 Right now I'm -1 on this as being such an edge case as to be not worth an
 option. If counting the rows in a table is too slow to be used, then there
 are going to be plenty of other options querying that table as well.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8408#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to