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.
This patch (that works on top of the IntervalStyle patch I
posted earlier today) adds support for ISO8601 standard
"Time Interval" "Durations" of the "format with designators"
(section 126.96.36.199.1). The other ISO 8601 types of intervals
deal with start and end points, so this one seemed most relevant.
It builds on a patch I had earlier submitted back in 2003,
where people noted that we wanted sql-standard intervals
first; but I see that ISO 8601 intervals did make it to the
I updated the docs, but I still need to add regression tests,
so it's still a WIP, but I think the code's ready (I've been
using an older version of this patch internally since '03) so
I'd appreciate feedback.
In response to
pgsql-hackers by date
|Next:||From: Reg Me Please||Date: 2008-10-02 10:31:47|
|Subject: Re: Transactions within a function body|
|Previous:||From: Heikki Linnakangas||Date: 2008-10-02 10:27:14|
|Subject: Re: trivial patch for pg_freespacemap documentation|