#16583: Explicitly passing a date to a DateTimeField in a model's create method
should override auto_now_add
-------------------------------------+-------------------------------------
Reporter: ian | Owner: nobody
Type: Bug | Status: reopened
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: | Keywords:
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by ian):
* status: closed => reopened
* resolution: invalid =>
Comment:
I realize it works this way, but I don't agree that it is the correct
behaviour. Based on PEP8, I would claim that this is being implicit,
rather than explicit, and not pythonic. Any other field that has a
default can be overridden.
No explanation as to ''why'' the behaviour is as it is, only that it is,
and pointing me to the documentation does NOT make it correct.
--
Ticket URL: <https://code.djangoproject.com/ticket/16583#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
