#26131: model field choices are not enforced
-------------------------------------+-------------------------------------
Reporter: stiffupperlip | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => invalid
Comment:
As described in the
[https://docs.djangoproject.com/en/stable/ref/models/instances
/#validating-objects validation documentation],
Note that `full_clean()` will not be called automatically when you call
your model’s `save()` method. You’ll need to call it manually when you
want to run one-step model validation for your own manually created
models.
--
Ticket URL: <https://code.djangoproject.com/ticket/26131#comment:4>
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/071.0e6a4887235aa0c4f2eedef3a4380ed6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
