From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Rajesh Kumar Mallah <mallah(at)trade-india(dot)com>, Christoph Haller <ch(at)rodos(dot)fzk(dot)de>, pgsql-sql(at)postgresql(dot)org, jasiek(at)klaster(dot)net |
Subject: | Re: Formatting intervals.. |
Date: | 2003-03-21 10:30:11 |
Message-ID: | 20030321103010.GA7635@zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Fri, Mar 21, 2003 at 11:05:32AM +0100, Peter Eisentraut wrote:
> Karel Zak writes:
>
> > test=# select to_char('3month 15d 4h 10m'::interval, 'DD-Mon HH24:MI:SS');
> > to_char
> > -----------------
> > 15-Mar 04:10:00
>
> This doesn't seem correct. First, you can't make "March" out of "3
> months". Second, 3 months, 15 days and some hours after the start of the
> year (if that definition were valid, which it isn't) is on March 16.
The interval_to_char() calls interval2tm() and from 'tm' creates output like
each other to_char() function.
You can try to write better interval2tm() for fix it. I haven't time for this now.
> Third, why do you have to write "HH24"? Surely no one would want to write
> out intervals using a 12-hour clock?
select to_char('5d 13h 10m 5s'::interval, 'HH or HH24:MI:SS');
to_char
----------------
01 or 13:10:05
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
From | Date | Subject | |
---|---|---|---|
Next Message | Popeanga Marian | 2003-03-21 11:00:29 | Re: explain |
Previous Message | Peter Eisentraut | 2003-03-21 10:05:32 | Re: Formatting intervals.. |