From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, 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:41:06 |
Message-ID: | Pine.BSF.4.21.0009181240260.17831-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 18 Sep 2000, Tom Lane wrote:
> 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?
first thing off the top of my head ... was there a reason why it was added
to contrib/odbc? ignoring the "oracle documentation", is it something
that is/was needed for ODBC?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2000-09-18 15:57:27 | RE: WAL & MVCC |
Previous Message | Tom Lane | 2000-09-18 15:37:41 | Re: Re: pg_dump tries to do too much per query |