| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | zakkr(at)zf(dot)jcu(dot)cz |
| 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:52:18 |
| Message-ID: | 20020711.175218.35815387.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2002-07-11 09:04:59 | Re: Proposal: CREATE CONVERSION |
| Previous Message | Karel Zak | 2002-07-11 08:38:22 | Re: Proposal: CREATE CONVERSION |