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:36 -0400 |
| commit | 625480cf0862f5998ed7e1e324087e58f8a740a7 (patch) | |
| tree | 79e6b654e0eedcce9d90d554fa955d53aece0fa2 /docs/ref | |
| parent | fd3dccb8dd4a7ae0ce5e5e5af25452bfca4462a7 (diff) | |
[1.7.x] Fixed #23631 -- Removed outdated note on MySQL timezone support.
Thanks marfire for the report.
Backport of 9db3653670 from master
Diffstat (limited to 'docs/ref')
| -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 dde56a384e..7822b615f4 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -517,11 +517,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. |