Thanks for your interst but no. this is a very odd Database UNIMS and were
stuck to it.
We have a windows Driver and a Unix driver.
I tested some type 3 Drivers but they are intended for network connections
and not local and are 200% slower than the 'not recommended' ODBC-JDBC
bridge'
But I'm pretty sure it has nothing to do with this driver because simple old
fashioned prepared stamentes with placements (?) works on both boxes.
Integer telerNummer = *new* Integer(131505);
Short productNummer = *new* Short("310");
Integer weekNummer = *new* Integer(200852);
String sorteringNaam = "PGE55";
Integer mutatieDatum = *new* Integer(200847);
Short percentage = *new* Short("11");
PreparedStatement ps = conn.prepareStatement(sql);
ps.setShort(1, percentage);
ps.setInt( 2, mutatieDatum);
ps.setInt(3, telerNummer);
ps.setShort(4, productNummer);
ps.setInt(5, weekNummer);
ps.setString(6, sorteringNaam);
*int* retval = ps.executeUpdate();
2008/11/25 Nicholoz Koka Kiknadze <[EMAIL PROTECTED]>
>
>>
>>> 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 test with JDBC
> driver for your database?
>
>
>
>
