#27684: Migrations accept default value for DateField that are not portable to
all
backends
-------------------------------------+-------------------------------------
Reporter: voodoo-burger | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: duplicate
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 Tim Graham):
* status: new => closed
* resolution: => duplicate
* component: Migrations => Database layer (models, ORM)
Comment:
As Avraham mentioned on the django-users thread, `DateField` is a
representation of `datetime.date`, so the `default` should be a `date`
object and not a string. I'm going to close this as a duplicate of #25417
since this is the essentially the same problem as reported there, just
applied to a different field.
--
Ticket URL: <https://code.djangoproject.com/ticket/27684#comment:3>
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/071.c16533e908fb7d420659b3a502b5f16a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
