| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Larry Rosenman <ler(at)lerctr(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: to_char(interval) --- done? |
| Date: | 2003-03-24 14:15:05 |
| Message-ID: | 20030324141505.GD23810@zf.jcu.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 24, 2003 at 09:56:53AM -0400, Alvaro Herrera wrote:
> > I volunteered to look into it, but got a sorta negative reply from Peter_E,
> > but no
> > response to my request for suggestions.
>
> I think what Peter was saying is to research some ways to manage
> intervals and other time related data types within what the SQL standard
> defines. to_char() and the like are only Oracle compatibility functions
> and should not be taken as serious ways to do things.
The to_char() knows formatting numbers, time/date to almost arbitrary
string. I unsure if SQL standard knows something like this and write
something for "interval" only is not good idea (IMHO) if there is a lot of
code which already know formatting data to string.
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-03-24 14:28:15 | Re: Threaded Python vs. PostGreSQL plpython |
| Previous Message | Alvaro Herrera | 2003-03-24 13:56:53 | Re: to_char(interval) --- done? |