#26984: Data Migrations and auto_now
-----------------------------+--------------------------------------
Reporter: fizista | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
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 charettes):
* status: new => closed
* resolution: => wontfix
Comment:
I'll resolve as ''wontfix'' in this case as migrations were designed to
carry model state around in order to make models available through
`RunPython` operations behave just like normal models would at certain
point in a project.
I see no compelling reason to make `auto_now` or `auto_now_add` behave
differently when used in data migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/26984#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/065.80aba28aadda7fe04357710f31cfed65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
