Re: Encoding Issue with UNICODE

From: "Magnus Naeslund(t)" <mag(at)fbab(dot)net>
To: Fritz Bayer <fritz-bayer(at)web(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Encoding Issue with UNICODE
Date: 2005-04-11 17:05:49
Message-ID: 425AAE6D.6080008@fbab.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fritz Bayer wrote:
> Hello,
>
> I`m using postgresql 7.2.1. According to the following lines data in
> my database gets encoded as unicode. Server and client communication
> seems to use unicode as well:
>
> woody=# select version();
> version
> ---------------------------------------------------------------
> PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.95.4
> (1 row)
>
> woody=# select getdatabaseencoding();
> getdatabaseencoding
> ---------------------
> UNICODE
> (1 row)
>
> woody=# show client_encoding;
> NOTICE: Current client encoding is 'UNICODE'
> SHOW VARIABLE
>
> I have a java program, which writes words containing german umlauts
> like äöü into the database. As you probably know, those characters
> belong to the ISO-8859-1 character encoding set.
>
> In my java webapplication those umlauts (äöü) get displayed correctly.
> So they actually get stored correctly in the database.
>

I know I had to set the charSet option in the connection URL to get
stuff working once:

"jdbc:postgresql://server/database?charSet=LATIN1"

Maybe that would work for UNICODE?

Regards,
Magnus

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim Strickland 2005-04-11 17:09:46 unsubscribe
Previous Message Richard Huxton 2005-04-11 17:01:41 Re: Data Mart with PostgreSQL (Please!)