Greetings all,
Just focusing on a sub topic here. I just browsed the JDBC 2.0 API
spec, and it looks like the main issue is ability to compile the
driver. Correct me if I'm wrong, but the new Driver, as Peter stated,
will largely have *more* methods in the existing classes, and a few new
supporting classes and types. The 1.2 JVM will support both drivers, as
stated in the spec.
I think that the integration of the 1.2/JDBC 2.0 spec into the driver is
the "right thing", but the JVM issue is still at the heart of the
matter. I think the distribution of the binary classes as both a 1.1x
and 1.2 jar file will be needed, due to the post which reflects the
reality that not too many of us have multiple JVMs on the platforms.
Our shop is using the 1.1 and postgresql pretty intensely here, but if
we can move to the 1.2, especially with the additional functionality the
JDBC 2.0 spec represents in BLOBs, and fixed meta and type classes, as
well as new result sets capabilities, it may be a case where the 1.1
development is frozen except for bug fixes anyway. I don't know if that
is the intent, but it makes sense from my point of view.
Now, my rambling does have one other purpose. Would a 1.2 compiled
binary work on a 1.1 system/app/applet anyway? It appears to me that it
would from a theoretical standpoint, as the interface additions and new
classes wouldn't be used. However, the internal algorithms and
interactions may make the assumption incorrect.
Cheers,
Dallas