On Thu, Jan 19, 2012 at 12:15 PM, Carl Meyer <c...@oddbird.net> wrote: > I don't think Adrian is proposing anything as extensive as #17. What > he's proposing (IIUC) wouldn't change the semantics of your sample code > at all. All it would do is prepopulate the FK field on the results of a > reverse-FK query, so the innermost "book.author" here doesn't need to do > a query: > > for author in Author.objects.all(): > for book in author.books.all(): > book.author > > There wouldn't be any action-at-a-distance with other Book instances.
Right, what Carl said -- no action-at-a-distance, just mere cache population on each related object. I don't think there would be a risk of backwards-incompatible side effects. Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.