On Sat, Jan 9, 2010 at 7:46 AM, Ivan Sagalaev <[email protected]>wrote:
> I too would opt for an implementation that makes model validation optional, >> i.e., a call that developers must explicitly make, if they choose, before >> saving a model. >> > > I'm +1 on some way of validating a form without *fully* validating a model. > But for a bit different reason that I didn't see in this thread yet. > I don't see why model validation should be bound up with forms at all. The current release notes for model validation state that it won't be done unless explicitly requested by the developer, and it seems that validating the model inside a form (whether fully or partially) breaks that contract. Again - pardon my ignorance if there's something that I'm missing. I was just alarmed to find a thread about forms + model validation given the current state of the release notes. Tobias -- Tobias McNulty Caktus Consulting Group, LLC P.O. Box 1454 Carrboro, NC 27510 (919) 951-0052 http://www.caktusgroup.com--
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?hl=en.
