diff options
| author | Tim Graham <timograham@gmail.com> | 2014-10-10 15:18:54 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-10-10 15:22:40 -0400 |
| commit | 0a31b4ea8e844f6b2f02027ef4d94b09c34ebb91 (patch) | |
| tree | f7074066e43d5000ef114154120c2dd3c22f073c | |
| parent | e24b246e2b9651fab08e0104293d65ee283d27c0 (diff) | |
[1.6.x] Fixed #23631 -- Removed outdated note on MySQL timezone support.
Thanks marfire for the report.
Backport of 9db3653670 from master
| -rw-r--r-- | docs/ref/databases.txt | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 1aabe59d4b..7055834318 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -494,11 +494,6 @@ for the field. This affects :class:`~django.db.models.CharField`, 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. |