Alex Sokoloff <[email protected]> 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
