Re: multibyte support [Resolved] - Mailing list pgsql-general

From Ma Siva Kumar
Subject Re: multibyte support [Resolved]
Date
Msg-id 200311131015.00767.siva@leatherlink.net
Whole thread Raw
In response to Re: multibyte support  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: multibyte support [Resolved]
List pgsql-general
On Wednesday 12 Nov 2003 8:40 pm, Tom Lane wrote:

> I think there is some confusion between you and the database about
> character set encoding.  Double check what the database encoding is
> (psql \l will tell you).  And double check what the system thinks the
> client-side encoding is ("show client_encoding" and/or \encoding).

Thanks for the suggestions. In a psql session, \l shows the encoding of the
database as unicode (in Name, Owner, Encoding form) and both \encoding and
show client_encoding; return unicode.

But it turned out that the problem is not with the database, but with the
client application (php). When I entered Chinese characters into the database
through psql client, it IS stored as chinese characters and works as
expected.

This I found out when Mark Rappoport suggested to configure php to handle
multibyte strings. The version of php I run is not handling the multibyte
string entered in the forms properly. I need to recompile php with
--enable-mbstring (http://www.php.net/manual/en/ref.mbstring.php) to solve
the problem.

Thanks everyone for the help.


Integrated Management Tools for leather industry
----------------------------------
http://www.leatherlink.net

Ma Siva Kumar,
BSG LeatherLink (P) Ltd,



pgsql-general by date:

Previous
From: "Craig O'Shannessy"
Date:
Subject: Re: RHEL
Next
From: Alex
Date:
Subject: Re: PL/PGSQL functions suddenly not working