On Tue, Jan 5, 2010 at 8:41 PM, Aristotle Miternan <[email protected]>wrote:
> Oops, taking a second look, I think you are right, the object I was > using to test that had its __unicode__ method calling something that > shouldn't exist yet. I guess this example was not complex enough. > > However, I think that I have figured out the problem. Model validation > was introduced in the latest patch, but I don't really understand how > it is different from what was before (not much explanation in the > docs). However, it seems that in ModelForms, clean() calls > self.instance.full_validate(). The problem with this is that I don't > necessarily have a >saved< instance assigned to the model yet. I don't > have enough data to save it before the form is evaluated! It seems > that I can work around this behavior by writing an overloaded > full_validate on my model, but this sounds flakey to me. Any thoughts? > > It would really help if you could show a minimal example of code that demonstrates the problem. Karen--
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?hl=en.
