Re: [HACKERS] Multibyte in autoconf
От | Tatsuo Ishii |
---|---|
Тема | Re: [HACKERS] Multibyte in autoconf |
Дата | |
Msg-id | 19991208162304M.t-ishii@sra.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] Multibyte in autoconf (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Multibyte in autoconf
Re: [HACKERS] Multibyte in autoconf Re: [HACKERS] Multibyte in autoconf |
Список | 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
В списке pgsql-hackers по дате отправления: