innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #14320 - Add a note about lack of timezone support in MySQL. Thanks RauntyDave for the suggestion, adamv for the patch. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15078 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Timo Graham 2010-12-28 13:35:48 +00:00
parent d3d345576d
commit 4919aaee11
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/ref/databases.txt
View File

@ -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 column types have a maximum length restriction of 255 characters, regardless
of whether ``unique=True`` is specified or not. 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:
SQLite notes SQLite notes