Of course, if an alias for ichar is carried forward I
can write code for the current postgres that won't
break with future releases. I realize that I might end
up being the only person on the planet who ends up
using ichar, and that may not be sufficient
justification for an alias....

Best,

Alex

--- Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> New proposal: forget ichar(), give the function two
> entries chr() and
> char().
> 
> 			regards, tom lane


__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

Mon, 18 Sep 2000 15:25:48 -0700 (PDT)
Alex Sokoloff <alex_sokoloff@yahoo.com>
Re: ascii to character conversion in postgres 
Alex Sokoloff <alex_sokoloff@yahoo.com> writes:
> Of course, if an alias for ichar is carried forward I
> can write code for the current postgres that won't
> break with future releases. I realize that I might end
> up being the only person on the planet who ends up
> using ichar, and that may not be sufficient
> justification for an alias....

Well, we will certainly have chr(), so why not save yourself the
trouble of converting later and make that alias today?

create function chr(int4) returns text as 'ichar'
language 'internal' with (iscachable);

ought to do it in 7.0.*.

			regards, tom lane

Tue, 19 Sep 2000 11:17:29 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: ascii to character conversion in postgres 