You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Tuan Luu <tu...@gmx.ch> on 2004/03/25 09:39:47 UTC
German Characters cause Problem in Database Insert
Hi
I have a PostgreSQL Database. Data is stored with SQL Transformer into the
database. But when I make a select on that table, I see strange symbols
instead of the ä, ü, à or è.
Is there something wrong with the character settings or localization in
cocoon?
I have cocoon 2.1.2, tomcat 4.1.29, mod_jk2, apache 2.0.48, Postgresql 7.4.
The Database was initdb - lized with de_CH.ISO8859-1, I have also tried
de_CH.
(I'm from Switzerland).
--
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: German Characters cause Problem in Database Insert
Posted by Yves Vindevogel <yv...@implements.be>.
Hi,
Try this:
Set up your connection as :
<dburl>jdbc:postgresql://myserver/mydatabase?charSet=ISO-8859-1
This worked for me (a lot of times)
Unfortunately, I also have problems, but working on them, think this is
JDK related
Alexander Schatten has a similar problem
On 26 Mar 2004, at 03:25, Joerg Heinicke wrote:
> On 25.03.2004 09:39, Tuan Luu wrote:
>
>> Hi I have a PostgreSQL Database. Data is stored with SQL Transformer
>> into the
>> database. But when I make a select on that table, I see strange
>> symbols
>> instead of the ä, ü, à or è. Is there something wrong with the
>> character settings or localization in
>> cocoon?
>> I have cocoon 2.1.2, tomcat 4.1.29, mod_jk2, apache 2.0.48,
>> Postgresql 7.4. The Database was initdb - lized with de_CH.ISO8859-1,
>> I have also tried
>> de_CH. (I'm from Switzerland).
>
> The error localization is not very exact. Nearly everything is
> possible at the moment: the SQLTransformer gets already corrupted
> characters, the SQLTransformer itself breaks them, the database has a
> wrong encoding, the select happens with a wrong encoding, and at the
> end it can be possible that the output encoding is not correct. You
> see you must localize the error, the best thing for doing this is
> probably remote debugging. MySQL offers a profileSql=true as
> additional parameter to the database URL, maybe PostgreSQL provides
> something similar. Tomcat 4.1.29 can be a problem
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=26997), but should
> not if you have everything in ISO-8859-1 as this charset is the
> default.
>
> Joerg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
>
Met vriendelijke groeten,
Bien à vous,
Kind regards,
Yves Vindevogel
Implements
Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76
Web: http://www.implements.be
First they ignore you. Then they laugh at you. Then they fight you.
Then you win.
Mahatma Ghandi.
Re: German Characters cause Problem in Database Insert
Posted by Joerg Heinicke <jo...@gmx.de>.
On 25.03.2004 09:39, Tuan Luu wrote:
> Hi
> I have a PostgreSQL Database. Data is stored with SQL Transformer into the
> database. But when I make a select on that table, I see strange symbols
> instead of the ä, ü, à or è.
>
> Is there something wrong with the character settings or localization in
> cocoon?
>
> I have cocoon 2.1.2, tomcat 4.1.29, mod_jk2, apache 2.0.48, Postgresql 7.4.
> The Database was initdb - lized with de_CH.ISO8859-1, I have also tried
> de_CH.
> (I'm from Switzerland).
The error localization is not very exact. Nearly everything is possible
at the moment: the SQLTransformer gets already corrupted characters, the
SQLTransformer itself breaks them, the database has a wrong encoding,
the select happens with a wrong encoding, and at the end it can be
possible that the output encoding is not correct. You see you must
localize the error, the best thing for doing this is probably remote
debugging. MySQL offers a profileSql=true as additional parameter to the
database URL, maybe PostgreSQL provides something similar. Tomcat 4.1.29
can be a problem
(http://issues.apache.org/bugzilla/show_bug.cgi?id=26997), but should
not if you have everything in ISO-8859-1 as this charset is the default.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org