Jacob Kaplan-Moss wrote:
>>
>> IsModified()
> 
> This could be useful, but it's probably not worth doing since Django  
> would have to keep two copies of all your data in memory to figure  
> this out.  Doubling the memory footprint of Django isn't on my wish- 
> list :)

One way to do it is to keep the "dirty" boolean flag, which can be set 
to True by any field modifications.

Thanks,

Eugene


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to