Does it need to be in Django itself? I'd think probably not, at least to start, but if there's something prohibiting that, then let us know.
On Tuesday, April 19, 2016 at 1:19:02 PM UTC-4, John Griebel wrote: > > I agree that we need a replacement; the current behaviour isn't all that > useful, IMHO. My vote would for choice #2, after all it seems more natural > (to me, at least), to think of numbers as a range, especially while > searching. Option 1 seems less intuitive for a situation like this. > > +1 from me, especially if we were to go with option 2. > > On Tue, Apr 19, 2016 at 10:46 AM, Omer Korner <omerk...@gmail.com > <javascript:>> wrote: > >> This is a proposal for a new ListFilter subclass. >> >> Currently, if you add a numeric field to list_filter, Django admin >> outputs all possible values of that field using AllValuesFieldListFilter. >> This can get ugly very quickly. >> For example, in my case, I have an application that manages transactions >> (orders) from an ecommerce site, and saves the transaction value. I can't >> easily filter the values (hundreds of thousands of them). >> >> I have two suggestions for a replacement, instead of outputting all >> available values for a numeric field: >> >> >> 1. Output something similar to what DateFieldListFilter does, eg. "10 >> or less/more, 15 or less" and so on, depending on real values. >> >> >> >> <https://lh3.googleusercontent.com/-vtH7qmf61l0/VxZDq_HOHNI/AAAAAAAAK7w/SGwtgU-rABEihmO-tNfzhl944FC-rVUGgCKgB/s1600/Screenshot%2Bfrom%2B2016-04-19%2B17%253A41%253A00.png> >> >> 2. A numeric input. These an be two inputs for a range, or a single >> input for a specific value. Looking at the ListFilter code, this would be >> a >> much more complex change. >> >> >> Happy to hear your thoughts. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/9ef08349-f6a6-48ed-bc30-5b62072fb749%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/9ef08349-f6a6-48ed-bc30-5b62072fb749%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/68790d91-2c2b-4cbd-b88e-3b0de99964ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
