From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | <zakkr(at)zf(dot)jcu(dot)cz>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <barry(at)xythos(dot)com>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: encoding names |
Date: | 2001-08-22 16:20:50 |
Message-ID: | Pine.LNX.4.30.0108221816160.679-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tatsuo Ishii writes:
> I don't think you need to change the function name "getdbencoding".
> "get_canonical_database_encoding" is too long anyway.
But getdbencoding isn't semantically different from the old
getdatabaseencoding. "encoding" isn't the right term anyway, methinks, it
should be "character set". So maybe database_character_set()? (No "get"
please.)
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-22 16:25:24 | Re: List response time... |
Previous Message | Oleg Bartunov | 2001-08-22 16:17:48 | Re: GiST patches for 7.2 (please apply) |
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-08-22 17:08:02 | Re: encoding names v2. |
Previous Message | Liam Stewart | 2001-08-22 14:59:38 | insert multiple rows attempt two |