From: Karel Zak <zakkr@zf.jcu.cz>
To: Stefan Weiss <spaceman@foo.at>
Cc: pgsql-sql@postgresql.org
Subject: Re: Formatting problems with negative intervals, TO_CHAR
Date: Mon, 7 Jun 2004 11:46:46 +0200
Message-ID: <20040607094646.GH28529@zf.jcu.cz> (raw)
In-Reply-To: <200406071108.37410.spaceman@foo.at>
References: <13d849b7ee63de04179c102cb25159d2@news.teranews.com>
<21474.1086561656@sss.pgh.pa.us>
<20040607075200.GA28529@zf.jcu.cz>
<200406071108.37410.spaceman@foo.at>
On Mon, Jun 07, 2004 at 11:08:37AM +0200, Stefan Weiss wrote:
> 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.
Ah.. ONLY the INTERVAL version of TO_CHAR() is deprecated! All others
versions for numbers, timestamp or date are supported now and in future
versions too.
Karel
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: zakkr@zf.jcu.cz, spaceman@foo.at
Subject: Re: Formatting problems with negative intervals, TO_CHAR
In-Reply-To: <20040607094646.GH28529@zf.jcu.cz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox