#34241: Django admin not showing seconds for list_display nor readonly
DateTimeField
-------------------------------+--------------------------------------
     Reporter:  Petr DlouhĂ˝    |                    Owner:  nobody
         Type:  New feature    |                   Status:  closed
    Component:  contrib.admin  |                  Version:  4.1
     Severity:  Normal         |               Resolution:  wontfix
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  1
-------------------------------+--------------------------------------

Comment (by Petr DlouhĂ˝):

 {{{
 Thanks for the ticket, however I find it unusual to use the admin for
 debugging, especially so precise that seconds/milliseconds are needed. I'd
 recommend using the dbshell/shell console to search for specific
 rows/objects.
 }}}

 @Mariusz Felisiak Thank you for your answer, but I am feeling that it
 might be a bit out of sync with everyday production reality.
 It might not be debugging per se, but if I got report by other admin about
 some inconsistency in the data in admin interface I really don't want to
 open `shell/dbshell` just find at what second the record was created. That
 is addition substantial workload.

 More importantly the seconds might be very important even for many
 ordinary admin users. There might be several use-cases - for example:
 - The user made two duplicate payments at same minute and want to return
 one of them - then the seconds might help the admin to determine which to
 refund and which to keep (or find matching record in payment system).
 - Many other cases where the user needs to find matching record in some
 other external database/application.
 - Cases where there are several records created at same minute.
 - The table has higher load and there are several records created every
 minute.
 - The admin user might be experienced enough in working with the data to
 analyze the problem with data but not a programmer able to use
 `shell/dbshell` (and it might not be desired to give him the permissions).

 Overall I think that the only reason to hide the seconds from users might
 be compactness of the UX, but at the same time I feel that there should be
 some mechanism to either allow users to access the hidden data in whole
 admin interface or at least make it possible to easily configure the
 output data format in admin interface without need to change it
 systemwide.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34241#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018585c730e2-8bbd9c7a-ea9e-415b-bb73-4c1b77bdb733-000000%40eu-central-1.amazonses.com.

Reply via email to