#29549: Document that Field.choices are enforced by model validation
-------------------------------------+-------------------------------------
Reporter: Evgeny Arshinov | Owner: Tim
Type: | Graham
Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.11
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
As Simon said in #29655, "Enabling model validation on save is likely to
break a few things and degrade performance significantly. I don't think
that's a pattern we should encourage or support at this point. Django and
third-party applications simply don't expect ValidationError to be thrown
on save(), this effectively change the signature of the function."
Thus, a ticket suggesting that would be closed as wontfix unless a
discussion on the mailing list reaches a different conclusion.
--
Ticket URL: <https://code.djangoproject.com/ticket/29549#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.c24c42dad8b7f909cab78336b34d208f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
