|
Joe Pluta wrote: > I'll be interested to see the outcome of this. If there is a setting that > makes JDBC smart enough to handle this, it will be a very important setting > to know! Changing the user profile we used to connect to the iSeries to use CCSID 37 and LANGID ENU worked. > P.S. You should never use these symbols in field or variable names if your > code is intended to run internationally. If they don't teach this in DBA > 101, they should. I know it's not your database, but in order to remove a > lot of headache for the rest of the package's life, you may really want to > consider internationalizing your database and removing variant characters. No arguments. Chalk this up to the 'internationalism' of a US based programmer. Character set issues just aren't something that is at the tom of most peoples minds. Long term solution, I think, will be to remove the variant characters from column names in the tables we might need to access via JDBC. Speaking of which ... anyone know where I can find a list of 'variant' characters? Thanks all for the assistance. david
As an Amazon Associate we earn from qualifying purchases.
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.