I posted earlier about performance issues trying to display many books in one single page. I've since fixed the problems by reducing the number of SQL queries from 12 per book, to just 11 overall. I also perform filtering based on user's permissions up-front. Big performance boost.
I ended writing several managers. Typing almost the same code in each manager. Encapsulating it all in a hand-crafted select_related_ex() that also fetches ManyToManyField's and ForeignKey's where "null=True". It occurred to me that such code could/should probably be made generic and part of the standard Django distribution. Has any thoughts already been dedicated to this? Is it only a question of time/priorities that it has not been included upfront? JJ. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
