Ron Mayer wrote:
> Ron Mayer wrote:
> > Tom Lane wrote:
> >> In fact, given that we are now
> >> somewhat SQL-compliant on interval input, a GUC that selected
> >> PG traditional, SQL-standard, or ISO 8601 interval output format seems
> >> like it could be a good idea.
> Attached are updated versions of the Interval patches ...
# Patch 2:
ISO 8601 Formatted Interval Input and Output
This patch adds another IntervalStyle 'iso_8601' to output ISO 8601
Time Intervals of the "format with designators". These are a bit
more flexible than Sql Standard intervals in that (like postgres)
they can express both years and days in the same interval value.
Reason for the patch:SQL Standard Intervals are limited compared to
postgres in what they allow (no mixed year-month and day-time
components). ISO8601 intervals allow such intervals and are easier
for machines to parse than the traditional postgres formats.
This patch depends on the IntervalStyle patch mentioned above.
In response to
pgsql-hackers by date
|Next:||From: KaiGai Kohei||Date: 2008-11-01 00:47:25|
|Subject: Re: Please make sure your patches are on the wiki page|
|Previous:||From: Ron Mayer||Date: 2008-11-01 00:22:55|
|Subject: Re: Updated interval patches (SQL std output, ISO8601 intervals,
and interval rounding)|