Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list
at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
I keep reading about open issues, and deprecating certain things, and
patch removed, and patch
Peter Eisentraut wrote:
Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list
at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
I keep reading about open issues, and deprecating certain things,
Bruce Momjian wrote:
I keep reading about open issues, and deprecating certain things,
and patch removed, and patch readded. What is going on?
I think the patch just added is OK, no?
I don't know, but earlier the identical patch was rejected by you.
---(end of
Peter Eisentraut wrote:
Bruce Momjian wrote:
I keep reading about open issues, and deprecating certain things,
and patch removed, and patch readded. What is going on?
I think the patch just added is OK, no?
I don't know, but earlier the identical patch was rejected by you.
I
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I keep reading about open issues, and deprecating certain
things, and patch removed, and patch readded. What is going
on?
I think the patch just added is OK, no?
I don't know, but earlier the identical
Peter Eisentraut wrote:
Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
I keep reading about open issues, and deprecating certain
things, and patch removed, and patch readded. What is going
on?
I think the patch just added is OK, no?
I don't
[sNip]
ISO 8601 gives more specific names.
ISO 8601 Basic Format: P2Y10M15DT10H20M30S
ISO 8601 Alternative Format: P00021015T102030
ISO 8601 Extended Format: P0002-10-15T10:20:30
In a way, the Extended Format is kinda nice, since itÂ’s
almost human readable.
I
Peter Eisentraut wrote:
Bruce Momjian writes:
Is this ready for application? It looks good to me. However, there is
an Open issues section.
It would be more useful to implement the SQL standard for intervals first
instead of inventing more nonstandard formats for it.
OK, patch
Is this ready for application? It looks good to me. However, there is
an Open issues section.
---
Ron Mayer wrote:
Short summary:
This patch allows ISO 8601 time intervals using the format
with time-unit
And another open issues email.
---
Ron Mayer wrote:
Tom wrote:
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
Yes, but by the same token iso8601 isn't specific enough either.
ISO 8601 gives more
I have a working output-part (attached below, but I'm
still cleaning up the documentation so I'll submit another
one later)
Ugh. Something in this pc quoted some characters in the attachment.
Rather than trying to apply it, wait a couple days and I'll submit
an update where the docs
Is there a way of producing as well as reading this format? Or did I miss
something?
cheers
andrew
Ron Mayer said:
Short summary:
This patch allows ISO 8601 time intervals using the format
with time-unit designators to specify postgresql intervals.
Below I have (A) What these time
Tom wrote:
Ron Mayer [EMAIL PROTECTED] writes:
Compared to the ISO 8601 time interval specification, the
postgresql interval syntax is quite verbose. For example:
Postgresql interval: ISO8601 Interval
---
[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,
Ron Mayer [EMAIL PROTECTED] writes:
Tom wrote:
Er, don't we support that already?
Postgresql supports a rather bizzare shorthand that has a similar
syntax, but AFAICT, doesn't match ISO 8601 in any way that makes
it practical.
Well, it's *supposed* to match ISO, AFAICT (the comments in the
Ron Mayer [EMAIL PROTECTED] writes:
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)?
I don't really care for using that name for it --- for one thing, you
couldn't do
set datestyle
This has been saved for the 7.5 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
Feel free to submit an updated patch that rips out the old syntax, as
discussed, or replace this patch with a more comprehensive one.
Tom Lane wrote:
Perhaps one could argue that the postgres shorthand should
follow the ISO conventions, but I'd not want to break backward
compatability, incase someone out there is using '1H30M' and
expecting minutes instead of months.
I doubt anyone is using it, because it's
Tom wrote:
Ron Mayer [EMAIL PROTECTED] writes:
Tom wrote:
Er, don't we support that already?
...AFAICT, doesn't match ISO 8601...
Well, it's *supposed* to match ISO Unless ISO has put out
multiple specs that cover this?
Any way to tell if this is the case.
8601's the one I see
Ron Mayer wrote:
If I'm breaking backward compatability anyway, I'd be happy to tweak
things like this one too. Unless, of course someone can give me a
reason why we want fractional years rounded to months, but fractional
months are rounded to fractions of a second.
Ron Mayer.
PS:
Tom Lane writes:
Ron Mayer [EMAIL PROTECTED] writes:
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)?
I don't really care for using that name for it --- for one thing, you
couldn't do
Tom Lane writes:
Yes, but by the same token iso8601 isn't specific enough either.
Several of the other input formats we support have at least as good a
claim on that name.
The only input formats we support are along the lines of
@ 1 year 2 mons 3 days 4 hours 5 mins 6 secs
@ 1 year 2 mons 3
Short summary:
This patch allows ISO 8601 time intervals using the format
with time-unit designators to specify postgresql intervals.
Below I have (A) What these time intervals are, (B) What I
modified to support them, (C) Issues with intervals I want
to bring up, and (D) a patch
Ron Mayer [EMAIL PROTECTED] writes:
Compared to the ISO 8601 time interval specification, the
postgresql interval syntax is quite verbose. For example:
Postgresql interval: ISO8601 Interval
---
'1 year 6
24 matches
Mail list logo
