#26984: Data Migrations and auto_now
-----------------------------+--------------------------------------
Reporter: fizista | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
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):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi fizista,
I'm not sure I understand your request.
Using `auto_now` (just like any other `default` option) result in usage of
`DEFAULT` in `ADD FIELD` operations which is required when adding `NOT
NULL` fields (e.g. `DateTimeField(auto_now=True)`). What should be done
when such a column is added if we were to drop support for `default`
altogether?
--
Ticket URL: <https://code.djangoproject.com/ticket/26984#comment:1>
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.3df72b37874fb164afa2a59857faeef8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
