From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | peter_e(at)gmx(dot)net, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal: CREATE CONVERSION |
Date: | 2002-07-11 08:38:22 |
Message-ID: | 20020711103822.F1895@zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 11, 2002 at 05:26:01PM +0900, Tatsuo Ishii wrote:
> > Where/how is describe conversion between encoding id and encoding
> > name? (I maybe something overlook:-) I expect new encoding system
> > will extendable and encodings list not will hardcoded like now.
> > (extendable = add new encoding without PostgreSQL rebuild)
>
> User defined charsets(encodings) is under discussion and I believe it
> would not happen for 7.3.
>
> > BTW, the client site needs routines for work with encoding names too
> > (pg_char_to_encoding()). Hmm.. it can't be extendable, or yes?
>
> pg_char_to_encoding() is already in libpq. Or am I missing something?
It works with encoding table (pg_enc2name_tbl) and it's compiled
into backend and client too. It means number of encoding is not possible
change after compilation and you (user) can't add new encoding without
pg_enc2name_tbl[] change. I original thought we can add new encodings
on-the-fly in 7.3 :-) You're right.
IMHO implement "User defined charsets(encodings)" will problem for
current libpq design.
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-07-11 08:52:18 | Re: Proposal: CREATE CONVERSION |
Previous Message | Zeugswetter Andreas SB SD | 2002-07-11 08:32:16 | Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org |