From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | peter_e(at)gmx(dot)net, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Multibyte in autoconf |
Date: | 1999-12-08 07:23:04 |
Message-ID: | 19991208162304M.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> OK, so the proposal is
>
> configure: --enable-mb
> Enables compilation of MULTIBYTE code, does not select a default
Agreed.
> initdb: --pgencoding=FOO
> Establishes coding of database; it's an error to specify non-
> default encoding if MULTIBYTE wasn't compiled.
Agreed.
> If no --pgencoding, you get default (non-multibyte) coding even
> if you compiled with --enable-mb.
Not agreed. I think it would be better to give an error if no default
encoding is not sepecified if configured with --enable-mb. Reasons:
1) Users tend to use only one encoding rather than switching multiple
encoding database. Thus major encoding for the user should be properly
set as the default.
2) if non-multibyte coding such as SQL_ASCII is accidently set as the
default, and if a multi-byte user create a database with no encoding
arugument, the result would be a disaster.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-12-08 07:36:22 | Re: [HACKERS] Multibyte in autoconf |
Previous Message | Tom Lane | 1999-12-08 06:27:53 | Re: [HACKERS] Table aliases in delete statements? |