This is yet another reason why I don't think it would be reasonable to
expect field validation within the model.

I also think that introducing such a check would not only lure the user
into a false sense of security

If the validations were done using DB constraints (as per Anssi's reply)
then this would be a reasonable expectation, however as mentioned before
changes in the field data can come from multiple places and it is not safe
to assume that any data in the model is ever going to be valid.

Given the performance concerns and the minimal amount of benefit that
validating on save() would give,


On Fri, Oct 18, 2013 at 2:42 PM, Florian Apolloner <[email protected]>wrote:

>
>
> On Friday, October 18, 2013 4:28:21 AM UTC+2, Karen Tracey wrote:
>>
>> Wasn't there also concern for double validation performed during form
>> clean and then model instance save?
>>
>
> Yes, technically we would probably have to track the validation state per
> field and also track changes to it etc… :(
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/31648978-7105-422f-ad62-68943e324a04%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAHKQagEy%2B3F_0tCkeTBJ-QT4BOwrZqyGzwFsZx84i58HJyxrZw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to