| From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DateStyle (was Re: Per-database/schema settings) |
| Date: | 2000-07-07 13:33:50 |
| Message-ID: | Pine.LNX.3.96.1000707152154.29348A-100000@ara.zf.jcu.cz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 6 Jul 2000, Peter Eisentraut wrote:
> Thomas Lockhart writes:
>
> > I've been pretty resistant to having a fully-tailorable native output
> > capability, since it would be possible to generate date strings which
> > can not be correctly interpreted on input.
>
> Good point. Let them use to_char().
>
Small note, to_char() has good friend to_timestamp() and this second
routine must allow interpret all output from to_char() to PG internal
datetype.
test=# select to_timestamp( to_char( now(), '"perverse date/time: "Y,YYY
FMMonth-DD HH24:MI:SS'), '"perverse date/time: "Y,YYY FMMonth-DD
HH24:MI:SS') = now();
?column?
----------
t
(1 row)
Karel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2000-07-07 13:40:20 | Re: Per-database/schema settings |
| Previous Message | eisentrp | 2000-07-07 13:14:07 | Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios... |