On Wed, 2008-12-03 at 21:18 -0800, Nate wrote: > I have a form that requires more complex validation logic than is > provided through the default form.is_valid implementation. > > As an example, I have a form with properties A and B. One of A or B > must be set. If neither is set, a validation error should be raised. > Can someone show me an example of overriding is_valid()? Ideally, I > would want the validation error associated not with an individual form > field, but with the entire form.
I spent an entire afternoon of my life writing up the documentation for that a couple of months ago. An entire afternoon that I'll never get back. So read the docs! See http://docs.djangoproject.com/en/dev/ref/forms/validation/ . > Also, this kind of "business logic" probably belongs in the model > itself. Judging from previous threads, it looks like model validation > is a work in progress. Correct. > Is it ready in 1.0? No. A "must have" for 1.1, however. > What is the suggested > approach for what I want to accomplish? See above and http://www.pointy-stick.com/blog/2008/10/15/django-tip-poor-mans-model-validation/ . Basically, you fake it using form validation even if it's just for the model at the moment. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
