Looks like you missed one change in the docs:
try:
article.full_validate()
except ValidationError, e:
# Do something based on the errors contained in e.error_dict.
# Display them to a user, or handle them programatically.
Appears in
http://docs.djangoproject.com/en/dev/ref/models/in
Can we please get a final decision on this please?
- Farhan
On Dec 9 2009, 8:17 pm, Farhan Ahmad wrote:
> The existing patch and tests are coded to behave like this so those should
> be good. I added our discussion to the ticket for historical purposes. I
> don't have to do anything more from
> Sorry for the problems, folks.
Hey, no worries, thanks for the good work. Seems like a very usable
solution.
--
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 unsu
I just committed r12206 [1] which contains a few
backwards-incompatible changes to model validation. First off,
ModelForm used to validate your entire model and raise
UnresolvableValidationError for any model fields that had errors, but
were excluded from the form. Now, ModelForm will only validate
On Wed, Jan 6, 2010 at 12:49 PM, Simon Willison wrote:
> A couple of related tickets filed today about model validation:
>
> http://code.djangoproject.com/ticket/12513
> http://code.djangoproject.com/ticket/12521
This has been fixed in r12206 [1]. Could people who had issues please
check things o
