× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David Gibbs skrev:
Ashish Kulkarni wrote:
transactionRecord.setTransactionData(new String(rs.getString("myField").getBytes("UTF-8")));

I've been working with Japanese double byte data in DB2/400 tables recently and I don't have to do anything special when I run my application ... rs.getString("fieldname") should get you the Japanese data in Unicode.

So far so good.
Your jvm needs to be running in Japanese though.

But why this? Is this to read and write IFS files properly?

If I have understood correctly the UTF-8 files should read off disk properly into the internal Unicode representation (Japanese characters included) which in turn should communicate correctly over JDBC regardless of the JVM configuration. Any reason why this JVM is different?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.