Permalink
Browse files

Fixed #14320 - Add a note about lack of timezone support in MySQL. Th…

…anks RauntyDave for the suggestion, adamv for the patch.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15078 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent d3d3455 commit 4919aaee118b9fac0a809abcbb5dafa72f67bdf2 @timgraham timgraham committed Dec 28, 2010
Showing with 8 additions and 0 deletions.
  1. +8 −0 docs/ref/databases.txt
View
@@ -360,6 +360,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

0 comments on commit 4919aae

Please sign in to comment.