On 1/9/07, David Cramer <[EMAIL PROTECTED]> wrote: > 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.
As I said before, probably your best bet, if you can't use select_related, is to document obsessively and enforce a list of 'forbidden' attributes. Hacking away at Django to deny access to those attributes is a last-ditch effort to be used only if you have no chance whatsoever of trusting your template authors not to use the things you tell them not to use. But if you must go that route, look at how the template system handles the 'alters_data' attribute on methods and attributes; probably the cleanest thing would be to implement a similar 'fetches_data' attribute and hack the template system to refuse to resolve such attributes. -- "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 -~----------~----~----~----~------~----~------~--~---
