Name: krT82822 Date: 03/08/2000


java version "1.3.0rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)

the call to createStatement fails with or without parameters (concurrency,
type or none) with Interbase 5, with the jdbc/odbc bridge.

I enabled trace in odbc driver and it seems that the bridge is calling
SQLSetStmtOption/SQL_CURSOR_TYPE which is not supported by the driver
(ODBC Visig?nic - interbase 4.x).
it works fine with jdk 1.1.7 or jdk 1.2.2.

----------------

6 Mar 2000, email from user, in reply to our asking whether a newer ODBC driver might help resolve this:

ctually I would'nt like to use a newer driver because of (1st) licenses
costs (the ODBC driver is shipped with the Interbase license)
and (2nd) this problem is not really important for me (I am working on test
software and, as I mentionned, it works with the jdk1.2).

However, I think that if the 1.3 release of the jdk works this way, it could
be a real big pain for a lot of developpers
and that they would be very unhappy with a 'get latest xxx driver from yyy'
...
(find drivers +sell them to customers- , modify code, new distributions,
tests, new behaviours(strange(bugs?)?) , etc ...)


The best way would be to support both behaviours (the 1.2 behaviour for
older drivers that do not support this odbc call).



(Review ID: 102115)
======================================================================