Fixed #23631 -- Removed outdated note on MySQL timezone support.
Thanks marfire for the report.
This commit is contained in:
parent
06b11b617e
commit
9db3653670
|
@ -493,11 +493,6 @@ for the field. This affects :class:`~django.db.models.CharField`,
|
|||
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
|
||||
to zero when the time is stored.
|
||||
|
||||
|
|
Loading…
Reference in New Issue