#19716: Support microsecond precision in MySQL ORM DateTimeField
-------------------------------------+-------------------------------------
Reporter: erik@… | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by claudep):
* needs_better_patch: 0 => 1
Comment:
I have a good news and a bad news:
- the good news is that I found and fixed the source of the test failures
mentioned above (in `adapt_datetime_with_timezone_support`).
- the bad news is that we need a very recent version of MySQLdb (1.2.5
released on January 2 2014) to have a bug fixed when retrieving datetime
value with microseconds from the database, unless we obtain `None`. The
patch will need to check and document that limitation.
--
Ticket URL: <https://code.djangoproject.com/ticket/19716#comment:13>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/077.10d0ca0b90c9a71789d80ad9c65a1845%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
