Author: timo Date: 2010-12-28 07:36:12 -0600 (Tue, 28 Dec 2010) New Revision: 15079
Modified: django/branches/releases/1.2.X/docs/ref/databases.txt Log: [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. Modified: django/branches/releases/1.2.X/docs/ref/databases.txt =================================================================== --- django/branches/releases/1.2.X/docs/ref/databases.txt 2010-12-28 13:35:48 UTC (rev 15078) +++ django/branches/releases/1.2.X/docs/ref/databases.txt 2010-12-28 13:36:12 UTC (rev 15079) @@ -345,6 +345,14 @@ 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 -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
