pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Frank Bax <fbax@sympatico.ca>
Cc: pgsql-php@postgresql.org
Subject: Re: to_char replacement
Date: Wed, 2 Feb 2005 13:15:38 -0500 (EST)
Message-ID: <200502021815.j12IFcI01979@candle.pha.pa.us> (raw)
In-Reply-To: <5.2.1.1.0.20050201081957.00a06d80@pop6.sympatico.ca>

Frank Bax wrote:
> At 12:44 PM 1/24/05, Michael Fuhr wrote:
> 
> >On Mon, Jan 24, 2005 at 06:47:33PM +0200, Raul Secan wrote:
> >
> > > Hello, since to_char() function will no longer be available from
> > > PostgreSQL 8.1 ... I might need to change that from my scripts.
> >
> >Eh?  Where did you get the idea that to_char() was going away?  The
> >documentation says that to_char(interval, text) is deprecated and
> >will be removed, but it says nothing about removing the function
> >altogether.
> 
> 
> Raul is not the only one who misread that sentence.  I thought the same 
> thing when I read it last week.  Reading too quickly, I guess.  After 
> spending several minutes searching for a replacement function, I went back 
> a reread it, understanding it the second time.  Perhaps if 
> to_char(interval, text) were marked with (*) in table and then (*) note at 
> bottom, it would be clearer that this sentence does not apply to all arguments.

Agreed.  I think we were a little too concise in that statement. Here is
the updated wording:

      The 8.1 release will remove the <function>to_char()</> function
      for intervals.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (5+ messages)

Message-ID: <200502021815.j12IFcI01979@candle.pha.pa.us>
Permalink:  ../200502021815.j12IFcI01979@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200502021815.j12IFcI01979@candle.pha.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: pgman@candle.pha.pa.us, fbax@sympatico.ca
  Subject: Re: to_char replacement
  In-Reply-To: <200502021815.j12IFcI01979@candle.pha.pa.us>
  References: <5.2.1.1.0.20050201081957.00a06d80@pop6.sympatico.ca> <200502021815.j12IFcI01979@candle.pha.pa.us>

* 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