#31587: Django admin - list_filter visually selected for query using implicit
               Reporter:  Anael Mobilia  |          Owner:  nobody
                   Type:  Uncategorized  |         Status:  new
              Component:  contrib.admin  |        Version:  3.0
               Severity:  Normal         |       Keywords:
           Triage Stage:  Unreviewed     |      Has patch:  0
    Needs documentation:  0              |    Needs tests:  0
Patch needs improvement:  0              |  Easy pickings:  0
                  UI/UX:  0              |

 As [https://docs.djangoproject.com/en/3.0/topics/db/queries/#the-pk-
 lookup-shortcut described on the documentation], there is implicit use of
 Equivalents are :
 xxx_id    # __exact is implied
 xxx_pk   # __pk implies __id__exact

 Example app is in attachment.
 I generated a link on the contrib.admin (Country admin view) in order to
 be able to list all people living in a country.
 All the following links provides the same correct result (only people
 living on the country are displayed) :
         url = '<a href="{baseurl}?country__id__exact={country}">Show
         url = '<a href="{baseurl}?country__id={country}">Show
         url = '<a href="{baseurl}?country__pk={country}">Show

 On the destination admin view (People), I have set a list_filter on

 Only the first link select the currently filtered Country on the filter
 list (on the right of the screen on the People admin view), the two others
 links doesn't.

 As the last two selectors are shortcuts for the fully explicit form, I
 suggest to have the same render on the filter list (current value is

 Tested on Django 3.0.6.


Ticket URL: <https://code.djangoproject.com/ticket/31587>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to