#2443: Add IntervalField to database models
-------------------------------------+-------------------------------------
Reporter: ben.tucker@… | Owner: mjtamlyn
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: IntervalField | Triage Stage: Accepted
interval duration DurationField |
feature 1.8-alpha |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"57554442fe3e209c135e15dda4ea45123e579e58"]:
{{{
#!CommitTicketReference repository=""
revision="57554442fe3e209c135e15dda4ea45123e579e58"
Fixed #2443 -- Added DurationField.
A field for storing periods of time - modeled in Python by timedelta. It
is stored in the native interval data type on PostgreSQL and as a bigint
of microseconds on other backends.
Also includes significant changes to the internals of time related maths
in expressions, including the removal of DateModifierNode.
Thanks to Tim and Josh in particular for reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/2443#comment:63>
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/078.3b381d8e6a65e126b99636da0379f656%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
