Thread: to_char replacement

to_char replacement

From
"Raul Secan"
Date:
Hello, since to_char() function will no longer be available from PostgreSQL 8.1 ... I might need to change that from my scripts.
 
For example I had something like that, which you can see returns the day in the format I need:
 
SELECT TO_CHAR(some_date, 'DD-MM-YYYY') FROM some_table;
 
Is there anyway to do that without TO_CHAR?

Re: to_char replacement

From
Christopher Kings-Lynne
Date:
to_char() will still be around for dates, just not for intervals.  You
have nothing to worry about.

Chris

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.
>
> For example I had something like that, which you can see returns the day
> in the format I need:
>
> SELECT TO_CHAR(some_date, 'DD-MM-YYYY') FROM some_table;
>
> Is there anyway to do that without TO_CHAR?

Re: to_char replacement

From
Michael Fuhr
Date:
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.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

Re: to_char replacement

From
Frank Bax
Date:
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.


Re: to_char replacement

From
Bruce Momjian
Date:
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