Commit 483cddf2 authored by Timo Graham's avatar Timo Graham
Browse files

[1.2.X] Fixed #14320 - Add a note about lack of timezone support in MySQL.... 

[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
parent b0ce5fce

docs/ref/databases.txt

+8 −0
Original line number Diff line number Diff line
@@ -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