[EMAIL PROTECTED] wrote:
>
> Is there a way of producing as well as reading this format? Or did I miss
> something?
Not yet, but I'd be happy to add it.
My immediate problem was having some 'P1Y6M' intervals to load.
I posted this much largely because it was useful to me so might
help others, and to see if it was of interest to others and
get feedback on what else to change.
I'd be happy to make it produce the output, and have some style
questions for doing so.
I'd hate to trigger this output on the already-existing 'datestyle'
of 'ISO', since that would break backward compatability.
I do notice that 8601 has both "basic" and "extended" formats.
The "basic format" is more terse ('19980115' instead of '1998-01-15').
Would it be useful if I added a 'datestyle' of 'ISO basic' which
would produce the most terse formats ('19980115' for dates,
and 'P1Y1M' for intervals)?
Ron
PS: What's the best inexpenive way for me to know if this changed
at all between the final draft and the published standard?
> Ron Mayer said:
> > This patch allows ISO 8601 "time intervals" using the "format
> > with time-unit designators" to specify postgresql "intervals".
> >...
> > Much more info can be found from the draft standard
> > ftp://ftp.qsl.net/pub/g1smd/154N362_.PDF
> > The final standard's only available for $$$ so I didn't
> > look at it.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
