No, you are correct, it does not follow reverse foreign keys, at least not yet, there was a discussion about this a few days ago, if this is of importance to you, you could either held write the code for django to support following reverse foreign keys in select_related() or you could write the SQL manually.
On Apr 19, 12:57 am, meppum <[EMAIL PROTECTED]> wrote: > I read that to mean that it follows foreign key relationships "up" > from the child to the parent. Meaning that if you load > Parent.select_related() that parent.child_set() will not yet have been > loaded. Or did I read it wrong? > > On Apr 18, 7:24 pm, Peter Rowell <[EMAIL PROTECTED]> wrote: > > > Take a look at select_related(), it may be of some help, depending on > > how you define "parent" and > > "child".http://www.djangoproject.com/documentation/db-api/#select-related > > > "Returns a QuerySet that will automatically “follow” foreign-key > > relationships, selecting that additional related-object data when it > > executes its query. This is a performance booster which results in > > (sometimes much) larger queries but means later use of foreign-key > > relationships won’t require database queries." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
