select_related is horrible slow on 90% of large database queries, and I haven't managed to implement the functionality I want in it yet.
I'd like to come up with an optional, or simply, a solution for our framework, where designers do not get access to do the SQL through the template on related attributes. Yes, we have debugging that shows us every query. Yes, it's a HUGE pain in the ass to figure out what's actually executing these queries. I'll happily modify django for what I want, I just need some help on where to start... as I dug around for an hour or two the other day and couldn't see where exactly the related objects execute the lazy sql. If nothing else, I guess I could just modify the cursor routines to implement the blocking, and then the template.render method. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
