Malcolm Tredinnick said the following:
> See earlier threads for why transparent behaviour is not a very safe
> idea. If you override save(), for example, it's going to be very easy to
> end up with things not being saved. This is not common behaviour, so
> asking somebody to at least pass in an extra param or two isn't going to
> kill them.
Actually in the previous thread you only seem to have mentioned
overriding __setattr__ :)
However, I'm sure the issue could be worked around (even though it seems
pretty uncommon) - for instance, having __setattr__ create the dirty set
when it doesn't exist, and only have the partial updates kick in if it
does - so if you were to replace __setattr__ and didn't call the model's
version, it would just revert to saving everything.
--
Collin Grady
I bought some used paint. It was in the shape of a house.
-- Steven Wright
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
