On 27 sep, 05:18, Luke Plant <[email protected]> wrote: > On 27/09/11 03:23, Alex Gaynor wrote: > > Would you like to share your solution? I found it pretty difficult to > come up with anything that: > > 1) could be done on a per-query basis and > 2) didn't require changes to the code that would use the QuerySet > objects i.e. fully API compatible. > > The one avenue I didn't explore yet was proxying the entire model > instance, which I'm sure would work, but could have lots of annoying > corner cases with Python magic methods etc. > > Luke >
I once created django-selectreverse [1] to do something alike, but that did require changing your code (no API compat.) and was also somewhat limited. It would be very nice to have something in core for this. Koen 1: http://code.google.com/p/django-selectreverse/ -- 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.
