| From: | Stefan Weiss <spaceman(at)foo(dot)at> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Formatting problems with negative intervals, TO_CHAR |
| Date: | 2004-06-07 09:08:37 |
| Message-ID: | 200406071108.37410.spaceman@foo.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Monday, 07 June 2004 09:52, Karel Zak wrote:
> http://www.postgresql.org/docs/7.4/static/functions-formatting.html
>
> Warning: to_char(interval, text) is deprecated and should not be
> used in newly-written code. It will be removed in the next version.
This is news for me. Are there any suggestions what we should replace
TO_CHAR with? For example, we were using TO_CHAR to print timestamp
values in ISO format without milliseconds ("YYYY-MM-DD HH24:MI:SS" style),
regardless of the current datestyle setting.
I see only three solutions to do this without using TO_CHAR, and IMO none
of them are very attractive:
- do the formatting at the application level,
- change the datestyle for this query only
- an ugly construct using 6 EXTRACT functions
I hope there is a more elegant way to solve this...
Why was TO_CHAR deprecated anyway? It seemed to me like a very useful and
flexible way to do date/time formatting.
Tnx,
stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2004-06-07 09:46:46 | Re: Formatting problems with negative intervals, TO_CHAR |
| Previous Message | Karel Zak | 2004-06-07 07:52:00 | Re: Formatting problems with negative intervals, TO_CHAR |