#24033: Reimplement Interval type on Oracle
-------------------------------------+-------------------------------------
Reporter: shaib | Owner: mjtamlyn
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: oracle interval | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5ca82e710e2f92b8c5114492205c8764918407d3"]:
{{{
#!CommitTicketReference repository=""
revision="5ca82e710e2f92b8c5114492205c8764918407d3"
Fixed #24033 -- Use interval type on Oracle.
Use INTERVAL DAY(9) TO SECOND(6) for Durationfield on Oracle rather than
storing as a NUMBER(19) of microseconds.
There are issues with cx_Oracle which require some extra data
manipulation in the database backend when constructing queries, but it
handles the conversion back to timedelta objects cleanly.
Thanks to Shai for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24033#comment:3>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.4d485da6580a6aed376646d65b16b8a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
