| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
raised OverflowError.
|
|
|
|
|
|
|
|
|
|
Thanks Tim Graham for noticing the issue.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously, empty values were saved as strings.
|
|
|
|
|
|
|
|
|
|
fields.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks Flavio Curella and Berker Peksag for the initial patch.
|
|
Thanks Keryn Knight and Tim Graham for the reviews.
|
|
|
|
Forwardport of ae1d663b7913f6da233c55409c4973248372d302
from stable/1.8.x plus more.
|
|
|
|
|
|
|
|
|
|
|
|
timeline.
refs #8898
|
|
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.
|
|
|
|
Thanks vanschelven and expleo for the initial patch.
|
|
Uses native support in postgres, and char(32) on other backends.
|
|
unique field.
Thanks Keryn Knight for the suggestion.
|
|
|
|
|