On Wed, 2002-03-27 at 16:05, Elisabeth Julg wrote:
> Checking whether to build with multibyte character support... configure:
> error::
> SQL_ASCII, EUC_JP, EUC_CN, EUC_KR, EUC_TW,
> UNICODE, MULE_INTERNAL,
> LATIN1, LATIN2, LATIN3, LATIN4, LATIN5,
> LATIN6, LATIN7, LATIN8, LATIN9, LATIN10,
> KOI8, WIN, ALT,
> ISO_8859_5, ISO_8859_6, ISO_8859_7, ISO_8859_8
> Or do not specify an argument to the option to use the default.
If you do specify LATIN1 now you won't be able to use the backend with
LATIN9 when you want EURO support. It is better to specify the default
then enable the encoding when you do createdb (personal opinion).
I have a UNICODE database system on one machine and a default on another
and, well they don't get along...
Cheers
Tony
--
RedHat Linux on Sony Vaio C1XD/S
http://www.animaproductions.com/linux2.html
Macromedia UltraDev with PostgreSQL
http://www.animaproductions.com/ultra.html
