From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | Alex Sokoloff <alex_sokoloff(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ascii to character conversion in postgres |
Date: | 2000-09-18 15:21:47 |
Message-ID: | 14511.969290507@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> Not documented (from oracle_compat.c) in PG documentation:
> btrim()
> ascii()
> ichar()
> repeat()
> and about ichar() is nothing in Oracle documentation, it's knows chr()
> only...
Sounds to me like calling it ichar() was an error, then. Should be chr().
> Directly rename it, or add "alias" entry to the pg_proc?
The alias would only be useful to people who had been using it as
"ichar()" --- which is not many people, since it's undocumented ;-)
Furthermore, now that I look, it looks like ichar() was new in
contrib/odbc in 7.0 and has only recently been moved into the main
code.
I vote for just renaming it to chr(). Any objections?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-09-18 15:37:41 | Re: Re: pg_dump tries to do too much per query |
Previous Message | g.p.ciceri | 2000-09-18 14:23:29 | contrib module soundex in CVS snapshot (function returning text and TOAST ???) |