From: | Weiping He <laser(at)zhengmai(dot)com(dot)cn> |
---|---|
To: | Jeff Lu <jklcom(at)mindspring(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What is the difference between --enable-multibyte and |
Date: | 2002-03-24 15:11:28 |
Message-ID: | 3C9DECA0.DF7ED594@zhengmai.com.cn |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Lu wrote:
> Hi,
>
> My database is configured with --enable-multibyte. I thought this is
> what I needed to be able to store Chinese Characters. Is this a correct
> assumption? Anyhow, when I tried to write to the database with Chinese
> content, the content becomes jibberish. Do I need to enable unicode
> conversion? If that's the case, can I just run configure with
> --enable-unicode-conversion on my current database without any side
> effect on my data?
>
> Thanks
> -Jeff
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
when > 7.2 the --enalbe-unicode-conversion is auto enabled
when specifing --enable-multibyte.
for pre 7.2, only when you want to store data in database using unicode,
do you need to --enable-unicode-conversion, if not, for example, you are
using EUC_TW or other encoding (but not unicode), I think you don't need
to enable it. but to my expreience, enable unicode is better (which is the
default case when > 7.2). because you can use unicode autoconversion
facility to extend your client encoding (such as GBK etc.)
I think the only side effect to your application is speed.
regards laser
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Emberson | 2002-03-24 17:43:44 | Large Object Location in 7.3 |
Previous Message | Mark kirkwood | 2002-03-24 12:23:07 | Re: SQL Server performing much better?!?! |