On Tue, 13 Jul 2010 02:10:03 -0700 (PDT) Margie <margierogin...@gmail.com> wrote:
> It's hard for me to believe that no other developers have encountered > this same problem (the problem of having a ModelForm saved at a point > in the code where you have no control). I did face the same problem in a more straightforward application, I've a model with multiple submits, only one of them should actually modify the model instance. now the moment is_clean() is executed the instance gets modified. wasn't fun to track the related bugs. I read about this backward incompatible change in http://docs.djangoproject.com/en/dev/releases/1.2/#modelform-is-valid-and-modelform-errors but did not understand what it meant except in hindsight. I'm actually still not sure what the advice to pass a copy to the ModelForm constructor means (I suppose it could mean override __init__ and use copy.copy). cheers, Alaa -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
