#17174: The docs should mention, that MySql doesn't support microseconds
-------------------------------+--------------------
Reporter: jammon | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
MySQL doesn't store the microsecond part of a TimeField or DateTimeField,
which is accounted for in the code (in django/db/backends/mysql/base.py).
But the documentation doesn't mention this limitation.
Suggestion: Add this sentence to /en/dev/ref/databases -> MySQL Notes ->
Notes on specific fields -> DateTime fields:
MySQL does not support storing the microsecond part of a TimeField or
DateTimeField,
so the microsecond part of the data is truncated (set to zero).
(It cost me quite some time to find out, why the integration tests failed
on the staging server. I couldn't believe, that MySQL has such a
limitation. See the bug report from Feb 2005 (!)
http://bugs.mysql.com/bug.php?id=8523).
--
Ticket URL: <https://code.djangoproject.com/ticket/17174>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
