#21798: Model validation should complain if both `add_now` and `auto_add_now`
are
specified.
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: anonymous
Type: | Status: assigned
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 1
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 1 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by erikr):
Eh, pressed enter too soon there. Two more notes:
* If we also take `default` into account this warning, I definitely agree
with charettes that we should fix this. Particularly as the behaviour in
combination with `default` is a lot less obvious.
* There are basically two options here: we could issue a
DeprecationWarning, and add a field check in the next version, or just add
the field check now. We went for the latter in #20484, but that was a
little more severe: that actually broke in some conditions. If I
understand comment:9 correctly, charette is in favour of adding the check
now - I don't feel strongly either way.
--
Ticket URL: <https://code.djangoproject.com/ticket/21798#comment:12>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.bfee374fd70d38dec16d48dc633eb4f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
