#27684: Migrations accept default value for DateField that are not portable to
all
backends
-------------------------------+--------------------------------------
Reporter: voodoo-burger | Owner: nobody
Type: Bug | 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
-------------------------------+--------------------------------------
Comment (by voodoo-burger):
Replying to [comment:1 Tim Graham]:
> We tried to add a system check to validate model field defaults in
#25417 but failed to do so due to backwards compatibility. I'm unsure if
it's worth trying to make a similar change here given it will likely break
backwards-compatibility for some users who may be using this technique and
only care about supporting some databases.
How about a warning then when someone uses a notation other than YYYY-MM-
DD?
--
Ticket URL: <https://code.djangoproject.com/ticket/27684#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 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.b90211a4d737b4eadec19fe1994fc19d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
