Re: Encoding conversion problem
- From: Andrea <tol7481@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 06:22:22 -0800 (PST)
Hi Silvio,
the settings are taken from the DB2 instance of a customer (and I
can't change them). The very same code works, of course, without
problems with a DB2 instance configured with ISO-8859-1.
The problem arises also when a C program stores to DB a string with
non-IBM850 valid characters: another C program can read the string
without problems while Java can't; so the string is not corrupted when
saved to DB but someone (JDBC driver? Java I/O?) looses something when
I read the field with Resultset.getString(int index) and I can't
convert it correctly (or I haven't found the right way to do it yet,
if it exists...).
BTW: a test has been made on DB2 with a table with a field declared
CHAR(n) FOR BIT DATA and Java code works without problems reading and
writing non-IBM850 characters.
Having read your feedback (THANK YOU EVERYONE!) I would say that
there's no way to read back those characters in Java in my
application.
Thanks again,
Andrea
.
- Follow-Ups:
- Re: Encoding conversion problem
- From: Roedy Green
- Re: Encoding conversion problem
- From: Silvio Bierman
- Re: Encoding conversion problem
- References:
- Encoding conversion problem
- From: Andrea
- Re: Encoding conversion problem
- From: Roedy Green
- Re: Encoding conversion problem
- From: Andrea
- Re: Encoding conversion problem
- From: Silvio Bierman
- Encoding conversion problem
- Prev by Date: Re: Encoding conversion problem
- Next by Date: Re: Encoding conversion problem
- Previous by thread: Re: Encoding conversion problem
- Next by thread: Re: Encoding conversion problem
- Index(es):
Relevant Pages
|
|