From: | Ma Siva Kumar <siva(at)leatherlink(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Dennis Gearon <gearond(at)fireserve(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Rappoport <mark(at)nsa(dot)co(dot)il> |
Subject: | Re: multibyte support [Resolved] |
Date: | 2003-11-13 04:56:59 |
Message-ID: | 200311131015.00767.siva@leatherlink.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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,
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2003-11-13 05:04:24 | Re: embedded postgresql |
Previous Message | Craig O'Shannessy | 2003-11-13 04:52:40 | Re: RHEL |