#21798: Model validation should complain if both `add_now` and `auto_add_now`
are
specified.
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: anonymous
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"cb15231888df2545356ad307eaea07f36aa0e8e0"]:
{{{
#!CommitTicketReference repository=""
revision="cb15231888df2545356ad307eaea07f36aa0e8e0"
Fixed #21798 -- Added check for DateTime mutually exclusive options
Added DateTimeCheckMixin to avoid the use of default, auto_now, and
auto_now_add options together. Added the fields.E151 Error that is raised
if one or more of these options are used together.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21798#comment:17>
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.7939e1464a22985ce748f5c01d557b09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
