Re: Proposal: CREATE CONVERSION - Mailing list pgsql-hackers

From Karel Zak
Subject Re: Proposal: CREATE CONVERSION
Date
Msg-id 20020711103822.F1895@zf.jcu.cz
Whole thread Raw
In response to Re: Proposal: CREATE CONVERSION  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: Proposal: CREATE CONVERSION  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List 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
encodingis 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 encodingson-the-fly in 7.3 :-) You're right.
 
IMHO implement "User defined charsets(encodings)" will problem forcurrent libpq design.
   Karel

-- Karel Zak  <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz,
http://mape.jcu.cz


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org
Next
From: Tatsuo Ishii
Date:
Subject: Re: Proposal: CREATE CONVERSION