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:46 -0400 |
| commit | 643374bcf544dbcd1091539a9f3c832b5440fee2 (patch) | |
| tree | 2fe821b7d8d018596e698fd4c61370d77ce87b49 | |
| parent | f58392d8d8b68e2e7777768f39941cd995ce16e4 (diff) | |
| download | django-643374bcf544dbcd1091539a9f3c832b5440fee2.tar.gz | |
[1.4.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 269197946e..ba797d4438 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -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. |