Subject | Re: AW: [firebird-support] Cannot transliterate character between character sets. |
---|---|
Author | Mark Rotteveel |
Post date | 2013-07-23T15:10:25Z |
On Tue, 23 Jul 2013 15:40:46 +0200, "Olaf Kluge" <olaf.kluge@...>
wrote:
charset etc) in the connection string (or properties) with Jaybird. If you
don't, then Jaybird will use connection characterset NONE and use the
current default character set of the JVM for encoding strings to bytes to
send to the server and decoding bytes received from the server to strings.
This could explain transliteration issues.
Mark
wrote:
> Hello Tomasz,with
>
>
>
> I have created a stroed procedure to find the records. There are some
> the mm² (²) (pow) and I get the error messeage with ibexpert. But I wasthe
> wondering, our Java (jaybird) application displays me all records, also
> problematic. The charset is in every case ISO8859_1. What cen be thereason
> for this difference?Are you sure you are specifying are characterset (encoding, lc_ctype,
charset etc) in the connection string (or properties) with Jaybird. If you
don't, then Jaybird will use connection characterset NONE and use the
current default character set of the JVM for encoding strings to bytes to
send to the server and decoding bytes received from the server to strings.
This could explain transliteration issues.
Mark