On 11/15/11 2:32 AM, Knut Anders Hatlen wrote:
Rick Hillegas<[email protected]> writes:
I'm winding down the work on the remaining bits of JDBC 4.1. I am
testing a patch which changes the JDBC level reported by Derby's
drivers. See derby-5488-09-aa-jdbcMinorVersion.diff patch attached to
DERBY-5488.
After checking in this patch, Derby will report that its JDBC level is
4.1 if you are running on Java 6 or 7. If you are running on Java 5 or
1.4, the level will continue to be 3.0.
Since DatabaseMetaData.getJDBCMinorVersion() is supposed to return the
JDBC minor version number for the driver (not for the platform it's
running on) and we have a single JDBC 4 driver implementation that
implements both JDBC 4.0 and JDBC 4.1, I think it sounds reasonable that
our JDBC 4 driver always returns minor version 1.
Thanks, Knut. I seem to have started this discussion in two places: this
email thread and DERBY-5488. I am going to mouse your response into a
comment on that JIRA and consolidate the discussion there.
Thanks,
-Rick
