> I like having access to the models attributes, such as
> get_absolute_url, we use things like this quite a bit in our templates
You could relatively painlessly 'flatten' the attributes of the model
instances in place before rendering template, i.e.
spam.get_absolute_url = spam.get_absolute_url()
Or programatically
for attr, val in spam.__dict__ :
if type(val).__name__ == 'function' :
setattr( spam, attr, val() )
Clearly, related object members would have to be handled slightly
differently, and to save expense on SQL queries you might only want to
evaluate some subset of the object's attributes while deleting others.
But it seems to me that at some point you must specify precisely which
object members will be available to the template, and you might as well
generate a restricted version of the object when doing so.
G
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
