| From: | Thomas Lockhart <thomas(at)pgsql(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Fduch the Pravking <fduch(at)antar(dot)bryansk(dot)ru>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, josh(at)agliodbs(dot)com, hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Timestamp/Interval proposals: Part 2 |
| Date: | 2002-06-11 13:49:18 |
| Message-ID: | 3D05FFDE.31839DA5@pgsql.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I already said it. The to_char() is 'tm' struct interpreter and use
> > standard internal PG routines for interval to 'tm' conversion.
> The point is it should _not_ do that for interval.
I use the tm structure to hold this structured information. I *think*
that Karel's usage is just what is intended by my support routines,
though I haven't looked at it in quite some time. Let me know if you
want me to look Karel...
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ulrich Neumann | 2002-06-11 14:19:21 | Native Win32/OS2/BeOS/NetWare ports |
| Previous Message | Tom Lane | 2002-06-11 13:39:35 | Re: tuplesort: unexpected end of data |