Commit 643374bc authored by Tim Graham's avatar Tim Graham
Browse files

[1.4.x] Fixed #23631 -- Removed outdated note on MySQL timezone support.

Thanks marfire for the report.

Backport of 9db36536 from master
parent f58392d8
Loading
Loading
Loading
Loading
+0 −5
Original line number Diff line number Diff line
@@ -417,11 +417,6 @@ of whether ``unique=True`` is specified or not.
DateTime fields
~~~~~~~~~~~~~~~

MySQL does not have a timezone-aware column type. If an attempt is made to
store a timezone-aware ``time`` or ``datetime`` to a
:class:`~django.db.models.TimeField` or :class:`~django.db.models.DateTimeField`
respectively, a ``ValueError`` is raised rather than truncating data.

MySQL does not store fractions of seconds. Fractions of seconds are truncated
to zero when the time is stored.