#11460: Admin changelist shows no rows with a non-zero count where ForeignKeys 
are
used in list_display and data is bad
-------------------------------------------+--------------------------------
          Reporter:  afitzpatrick          |         Owner:  nobody
            Status:  reopened              |     Milestone:        
         Component:  django.contrib.admin  |       Version:  1.0   
        Resolution:                        |      Keywords:        
             Stage:  Unreviewed            |     Has_patch:  1     
        Needs_docs:  0                     |   Needs_tests:  0     
Needs_better_patch:  0                     |  
-------------------------------------------+--------------------------------
Changes (by afitzpatrick):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 I absolutely agree re garbage in garbage out: if there's a problem with
 the data, the admin tool should '''not''' be expected to work properly.

 However, if there's an obvious data problem, the admin tool shouldn't say
 "there's ten records" but only display nine. It just doesn't make any
 sense: clearly something is very wrong and we shouldn't pretend it's OK.

 No need to handle it gracefully: just make it throw a dirty great
 exception, rather than pretending everything is OK. Either data is OK, or
 it's not. At the moment the admin tool handles shades of grey, which is
 unnecessary and confusing. No?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11460#comment:2>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to