Changes between Version 1 and Version 2 of Ticket #16142

06/01/11 17:41:27 (4 years ago)


  • Ticket #16142 – Description

    v1 v2  
    33<jezdez> or point me to the section where the use case is described if this has been discussed before
    44<subsume> jezdez here's a test case I whipped up at the time
    5 * pgurumur ( has joined #django
    6 * bradleyayers ( has joined #django
    75<jezdez> subsume: why don't you use fm.Company.objects.filter(locations__zip_code="90210", locations__open_days="WEEKEND")?
    8 * shapr has quit (Quit: hometime, work is over)
    96<subsume> jezdez I certainly don't mind but that's not the QS that will be generated by the admin filter implementation in place
    107<jezdez> subsume: not you lost me, what exactly do you want?
    118<jezdez> *now
    129<subsume> I wanted a hook to override the broken behavior so I can achieve what you typed. Right now the filters will just loop over and over tacking on a new .filter() each time
    13 * j00bar (407ddf92@fsf/emeritus/j00bar) has joined #django
    14 * Finity (6c54d5e9@gateway/web/freenode/ip. has joined #django
    15 * seanbrant has quit (Quit: seanbrant)
    1610<subsume> Because in your case it was part of the same join. In the current implementation its not.
    17 * fission6 has quit (Quit: Leaving)
    1811<jezdez> subsume: okay, I must have missed that notion from the ticket, please open a ticket and state this exact reason. and no, this shouldn't be fixed with yet another hook, but by making the default filtering more effective in the first
    1912<jezdez> place
Back to Top