From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | per(at)mobilehits(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: UNICODE |
Date: | 2001-10-26 00:15:02 |
Message-ID: | 20011026091502K.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> To enable localization of our new platform, we thought that saving all
> character strings as UNICODE would be a good idea. Even if the front-end
> (PHP) doesn't fully support UNICODE yet, we figured it's still good to have
> the database in that format, for the future. We have not installed
> mb_string.
>
> We have created a UNICODE database and started experimenting with it
> (PostgreSQL)
> ./configure --enable-multibyte
> createdb -E UNICODE me-e
>
> My question is: do you need to convert strings to UTF-8 before adding them
> to the database, or is that done "automatically"?
PostgreSQL 7.1 can do the conversion in the backend side. You need to
add an option "--enable-unicode-conversion", however. Also, you need
to tell what kind of encoding you are using in your applications. To
do it in PHP4, you could use pg_set_client_encoding function.
If your PHP installation does not have it, you could issue a SQL:
set client_encoding to 'encoding_name_in_your_PHP_applicatoion';
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Ren Weili | 2001-10-26 01:08:16 | Chinese sort order problem |
Previous Message | Stephan Szabo | 2001-10-25 23:50:59 | Re: [LONGINT] Problem |