It's simply that the model wants to hold data that are not DB fields.
These additional data are calculated using DB data.

Currently, the model creates these data lazily when requested first
time. But calculating them with model-instance-creation would be
simpler and result in smaller code.

I assume I can -and have to- override __init__ as usual, call
models.Model.__init__(self, *args,**kwargs), and add my own attributes.
At least, the nice Wiki article above (thank you!) looks like there is
no "Magic" in the models, that could become defective.
 Ruben


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to