diff options
author | Bruce Momjian <bruce@momjian.us> | 2003-12-20 15:32:55 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2003-12-20 15:32:55 +0000 |
commit | 54c8e821b8313c78ba19653f74e83e956fdb8fe5 (patch) | |
tree | ca8409fb0a0a20e84b19accd2351192553120c3f /src/backend/tcop/postgres.c | |
parent | 7be614a087019bb0ed566e295bfbd47f1dd22cd0 (diff) | |
download | postgresql-54c8e821b8313c78ba19653f74e83e956fdb8fe5.tar.gz postgresql-54c8e821b8313c78ba19653f74e83e956fdb8fe5.zip |
In my mind there were two categories of open issues
a) ones that are 100% backward (such as the comment about
outputting this format)
and
b) ones that aren't (such as deprecating the current
postgresql shorthand of
'1Y1M'::interval = 1 year 1 minute
in favor of the ISO-8601
'P1Y1M'::interval = 1 year 1 month.
Attached is a patch that addressed all the discussed issues that
did not break backward compatability, including the ability to
output ISO-8601 compliant intervals by setting datestyle to
iso8601basic.
Interval values can now be written as ISO 8601 time intervals, using
the "Format with time-unit designators". This format always starts with
the character 'P', followed by a string of values followed
by single character time-unit designators. A 'T' separates the date and
time parts of the interval.
Ron Mayer
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions