On 27/09/11 03:23, Alex Gaynor wrote: > I'm not a fan of this, for a few reasons, firstly: because it feels > wrong for a QuerySet to execute multiple queries. This isn't a deal > breaker, just something that struck my conceptually initially. Second I > disagree that it's difficult to do outside of core, it's not as easy as > it ought to be, but it's very possible (citation: I've done it :)).
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 spilled spot remover on my dog. Now he's gone." (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- 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.
