From 483cddf23eaece8980ec771f0c0b298f91979e31 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Tue, 28 Dec 2010 13:36:12 +0000 Subject: [PATCH] [1.2.X] Fixed #14320 - Add a note about lack of timezone support in MySQL. Thanks RauntyDave for the suggestion, adamv for the patch. Backport of r15078 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15079 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/databases.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 0ac5caaf87..60a0f13d54 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -345,6 +345,14 @@ Furthermore, if you are using a version of MySQL prior to 5.0.3, all of those column types have a maximum length restriction of 255 characters, regardless 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. + .. _sqlite-notes: SQLite notes