[EMAIL PROTECTED] ("Magnus Naeslund(t)") wrote in message news:<[EMAIL
PROTECTED]>...
> 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?
>
As far I have heard the charSet property is ignored by the jdbc
drivers. However, somebody patched them an introduced this property.
> Regards,
> Magnus
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
