I have a large application where I make significant use of select_related() to bring in related model data during each original query.
As the application has grown, the select_related calls haven't completely kept up, leaving a number of scenarios where Django happily and kindly goes running off to the database to fetch related model rows. This significantly increases the number of database hits, which I obviously don't want. I've had some success in tracking these down by checking the queries generated using the django.db.connection.queries collection, but some remain unsolved. I've tried to find a suitable location in the django code to raise an exception in this scenario, making the tracking much easier, but tend to get lost in the code. Is anyone able to point me in the right direction for a suitable location for this? Thanks, Mark. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
