#34061: Model validations should be run on save()
-------------------------------------+-------------------------------------
Reporter: Aaron Smith | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: model, validation, | Triage Stage:
validations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Uncategorized => New feature
* resolution: => wontfix
Comment:
This behavior is by design and it's
[https://docs.djangoproject.com/en/dev/ref/models/instances/#validating-
objects documented] (as you've already noticed). If you want to change
design decisions then please first start a discussion on the
DevelopersMailingList, where you'll reach a wider audience and see what
other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features]. We must reach a strong consensus in the discussion
to move it forward.
> I propose we add a new `ValidatedModel` class that subclasses `Model`.
You can always add and use your own subclass in the code.
--
Ticket URL: <https://code.djangoproject.com/ticket/34061#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018387625e17-d40be5c4-93a0-4687-af5e-9a27c5b9ae0d-000000%40eu-central-1.amazonses.com.
