The only hard part is modifying the _validate_field_name method. get_query_set uses the regular filtering mechanism, so it actually works out of the box with the __ field spanning. I will provided a patch (once I clean up the code), then you can see that it is quite a small fix and may be worth integrating.
--Rory Geoghegan On Thu, Apr 5, 2012 at 3:46 PM, Adrian Holovaty <[email protected]> wrote: > On Thu, Apr 5, 2012 at 11:46 AM, Rory Geoghegan > <[email protected]> wrote: > > We currently have that code written. Is it worth turning that into a > > patch for contrib.sites, with unit tests et al, and pushing upstream > > into django? Should I fill out a bug? > > I don't think this added complexity/functionality is worth adding to > the framework. It's easy enough to make your own custom manager that > does the same thing. If you'd like to share it with others, toss it > online somewhere. > > Adrian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
