From 643374bcf544dbcd1091539a9f3c832b5440fee2 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Fri, 10 Oct 2014 15:18:54 -0400
Subject: [PATCH] [1.4.x] Fixed #23631 -- Removed outdated note on MySQL
 timezone support.

Thanks marfire for the report.

Backport of 9db3653670 from master
---
 docs/ref/databases.txt | 5 -----
 1 file changed, 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.