mirror of
https://github.com/django/django.git
synced 2025-03-25 08:40:45 +00:00
[1.6.x] Fixed #23631 -- Removed outdated note on MySQL timezone support.
Thanks marfire for the report. Backport of 9db3653670 from master
This commit is contained in:
parent
e24b246e2b
commit
0a31b4ea8e
@ -494,11 +494,6 @@ for the field. This affects :class:`~django.db.models.CharField`,
|
|||||||
DateTime fields
|
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.
|
|
||||||
|
|
||||||
MySQL does not store fractions of seconds. Fractions of seconds are truncated
|
MySQL does not store fractions of seconds. Fractions of seconds are truncated
|
||||||
to zero when the time is stored.
|
to zero when the time is stored.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user