Fixed #23631 -- Removed outdated note on MySQL timezone support.

Thanks marfire for the report.

1 files changed, 0 insertions, 5 deletions

diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 627412b0e3..689fedcffb 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -493,11 +493,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.