Jdbc2Odbc, Prepared Stmts and Batches... just don't work together.

Question

Hi.
this throws a NegativeArraySizeException on executeBatch:
con.setAutoCommit(false);
PreparedStatement p=con.prepareStatement("insert test_date(txt) values(?)");
p.setString(1, "das");
p.addBatch();
p.setString(1, "sss");
p.addBatch();
p.executeBatch();
con.commit();
p.close();
con.close();
this does too:
con.setAutoCommit(false);
PreparedStatement p=con.prepareStatement("insert test_date(txt) values(?)");
p.setString(1, "das");
p.addBatch();
p.executeBatch();
con.commit();
p.close();
con.close();
this works fine:
con.setAutoCommit(false);
PreparedStatement p=con.prepareStatement("insert test_date(txt) values(?)");
p.setString(1, "das");
p.addBatch();
p.executeUpdate();
con.commit();
p.close();
con.close();
to make things worse, this does not throw any Exception, but instead of a 5, I get 144595456 in the table!!!:
con.setAutoCommit(false);
PreparedStatement p=con.prepareStatement("insert test_date(l) values(?)");
p.setInt(1, 5);
p.addBatch();
p.executeBatch();
con.commit();
p.close();
con.close();
could someone recode Jdbc2Odbc?? :))
nikolas/

Answer 1

Hi,
As far as I know, this is a bug in the JDBC-ODBC bridge. I used to get the same error and I used a native driver to get around this problem. My database was DB2, and I used a native driver for DB2. One more thing, the JDBC-ODBC bridge is very slow and you will notice the difference once you use the native driver.
There is a batch file usejdbc2.bat which directs the driver to use the jdbc 2.0 specs explicitly. I ran that before actually using the native driver. In the case of a DB2 driver it should be in the directory Sqllib\java12. But I am not sure about the other drivers.
Hope this helps and best wishes,
Nish