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 09:04:59 |
Message-ID: | 20020711110459.I1895@zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 11, 2002 at 05:52:18PM +0900, Tatsuo Ishii wrote:
> > > 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.
>
> No, it's not a libpq problem, but more common "client/server" problem
> IMO. It's very hard to share dynamically created object (info)
> effectively between client and server.
IMHO dynamic object will keep server and client must ask for wanted
information to server.
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 09:30:48 | Re: Proposal: CREATE CONVERSION |
Previous Message | Tatsuo Ishii | 2002-07-11 08:52:18 | Re: Proposal: CREATE CONVERSION |