For what its worth;
I also tested it against the ibatis-2.3.4.726.jar build and all problems
occur the same.
2008/11/24 Corné A [EMAIL PROTECTED]
Hi all,
I am a happy ibatis user for years and now I have encountered a strange
thing.
I have Ibatis build with jdk 1.5.0_16 on my Windows XP.
Hi Clinton,
I did send the source jar which included the ibatis runtime changes source
code. Of course for the generator tool i sent just the binary.
Not an issue and i am happy that you responded. Will attach on the user
group for Prakash, and on the JIRA system once merged with current trunk.
When I deploy everthing to a Linux box I get the weirdest errors from the
Driver.
--- Cause: java.sql.SQLException: [unixODBC][INTERCHAIN][UNIMS-ODBC]
[UNIMS]
Well, maybe we can blame differences in ODBC layer? I've have never used
ODBC (or ODBC-JDBC bridge) on linux, any chance you can
Ok I tested my but off and here is what I found:
All fields from this database are or CHAR or NUMERIC (see bottom voor META
info)
the problematic columns both are NUMERIC without scale
vdperc DATA_TYPE:2 TYPE_NAME:numeric PRECISION:3 LENGTH:3 SCALE:0 RADIX:0
NULLABLE:1
vdmuwe DATA_TYPE:2
You can force Abator to generate BigDecimals for these fields with
this configuration setting:
javaTypeResolver
property name=forceBigDecimals value=true/
/javaTypeResolver
This might be better in your case as it seems that the UNIX driver has
some difficulty converting BigDecimals to Short or
Thanks Jeff ,
I noticed earlier that the BigDecimals I already had kept working. I swapped
al other Numerics to BigDecimals with the javaTypeResolver and hurray al
worked again.
Still it's strange that non BigDecimals work as Keys but not as values,
A fact is that it is a very odd database and
