On Fri, Mar 28, 2014 at 2:29 PM, anubhav joshi <[email protected]>wrote:
> > values() and values_list() are both intended as optimisations for a >> specific use case - retrieval of subsets of data without the overhead of >> creating a model instance. This metaphor completely falls apart when >> dealing with m2m relations, because the the "one row, one object" metaphor >> that underpins most of the ORM falls apart. >> >> I agree with you on this. "one-row,one-object" cannot be implemented here. > Well, it *can* be implemented - just not in a way that is both computationally efficient *and* backwards compatible. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_WmUA0G%2BsZb_tWAzr7MFYPLo50EC1dDvGQ-jnR3iywbw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
