Re: encoding again - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: encoding again
Date
Msg-id Pine.LNX.4.44.0309100054560.1210-100000@peter.localdomain
Whole thread Raw
In response to encoding again  (Kathy Zhu <Kathy.Zhu@Sun.COM>)
List pgsql-general
Kathy Zhu writes:

> 1) the sorting is based on unicode value, not EUC_CN encoding value.

The sorting is always based on the server encoding.  There is no way to
change that.

> 2) I wrote the ResultSet to a file by using OutputStreamWriter(file, "EUC_CN"). The
> file is not readable from the browser with any charset setting.

That is a problem in whatever client interface that is (Java?) or your
browser.

> 3) Changing client_encoding from UNICODE to EUC_CN actually alter/loose the data if
> you compare the above "select *" statements.

You're going to have to be a bit more specific, because many of us can't
identify the characters or see what is wrong with them.

Also, try a more recent PostgreSQL version, such as 7.3.4.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-general by date:

Previous
From: Jeff Eckermann
Date:
Subject: Re: Picture with Postgres and Delphi
Next
From: "Bruno BAGUETTE"
Date:
Subject: How to convert a UnixTimestamp to a PostgreSQL date without using ::abstime ?