On 1/9/07, David Cramer <[EMAIL PROTECTED]> wrote: > I want to setup some kind of blocking mechanism so that while rendering > a template the models will not do any SQL queries that have not already > been executed, or at least block the related field queries.
Unfortunately I think this would be viewed as gigantic "breakage" by many users of Django; being able to access attributes of an object -- even if those attributes involve database queries -- is simply too convenient to have in the template. Your best options are to either start using select_related (so that all data access happens immediately) or enforce some rules on your template authors; the automatic model documentation will tell you which attributes access data, so you will be able to isolate those and tell template authors not to use them. Failing that, serious hacking inside Django would be necessary; if you're willing and able to delve into the template system, you might be able to implement something akin to 'alters_data'; then you'd need a way to mark every data-accessing attribute of every model with a 'fetches_data' attribute. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
