#23631: Documentation: Outdated warning about DateTimeField on MySQL?
-------------------------------+--------------------
Reporter: marfire | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The [https://docs.djangoproject.com/en/dev/ref/databases/#datetime-fields
MySQL Database notes] say:
> MySQL does not have a timezone-aware column type. If an attempt is made
to store a timezone-aware time or datetime to a TimeField or DateTimeField
respectively, a ValueError is raised rather than truncating data.
I don't use MySQL so I can't check this, but isn't this wrong? Wasn't this
fixed in 1.4 by storing timezone-aware datetimes in UTC? This note goes
back to (at least) 1.3, so I'm guessing it was just never updated.
--
Ticket URL: <https://code.djangoproject.com/ticket/23631>
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/050.b50a0c58ac3dfbf9e518a6b867ad0b7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
