You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/02/17 18:39:24 UTC
[jira] Issue Comment Edited: (DERBY-4869) Implement JDBC 4.1, the
api increment introduced by Java 7
[ https://issues.apache.org/jira/browse/DERBY-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995945#comment-12995945 ]
Rick Hillegas edited comment on DERBY-4869 at 2/17/11 5:38 PM:
---------------------------------------------------------------
For two reasons:
I) We simply followed the pattern described in (c) above: JDBC 4.0 did not introduce any methods into java.sql.Driver that prevented implementations from being compiled on JDK 1.4. There was therefore no reason for DriverManager.getDriver() to return 2 different classes, one for Java 5 and lower and another for Java 6 and higher. Now, of course, there is a reason to do that.
II) Driver autoloading actually goes back to JDK 1.4. It's just that Java 6 introduced a new kind of driver autoloading. And Derby was out of compliance by not supporting the JDK 1.4 version of autoloading. The JDK 1.4 version of autoloading involves setting a system property which is a list of Drivers which should be autoloaded. The property is set when you boot the VM. It is described here: http://download.oracle.com/javase/1.4.2/docs/guide/jdbc/getstart/drivermanager.html
Hope this helps,
-Rick
was (Author: rhillegas):
For two reasons:
I) We simply followed the pattern described in (c) above: JDBC 4.0 did not introduce any methods into java.sql.Driver that prevented implementations from being compiled on JDK 1.4. There was therefore no reason for DriverManager.getDriver() to return 2 different classes, one for Java 5 and lower and another for Java 6 and higher. Now, of course, there is a reason to do that.
2) Driver autoloading actually goes back to JDK 1.4. It's just that Java 6 introduced a new kind of driver autoloading. And Derby was out of compliance by not supporting the JDK 1.4 version of autoloading. The JDK 1.4 version of autoloading involves setting a system property which is a list of Drivers which should be autoloaded. The property is set when you boot the VM. It is described here: http://download.oracle.com/javase/1.4.2/docs/guide/jdbc/getstart/drivermanager.html
Hope this helps,
-Rick
> Implement JDBC 4.1, the api increment introduced by Java 7
> ----------------------------------------------------------
>
> Key: DERBY-4869
> URL: https://issues.apache.org/jira/browse/DERBY-4869
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: Drv41.java, JDBC_4.1_Changes.html, derby-4869-01-ac-rs-getObject.diff, derby-4869-01-ad-rs-getObject.diff, derby-4869-02-aa-cs-ps-addBatch.diff, derby-4869-02-ab-cs-ps-addBatch.diff, derby-4869-03-aa-rs-getObject-errorCleanup.diff, derby-4869-04-aa-rs-getObject-simplification.diff, derby-4869-05-aa-rs-getObject-exception.diff, derby-4869-06-aa-cs-getObject.diff, derby-4869-06-ab-cs-getObject.diff, derby-4869-07-aa-timedisplacement.diff, derby-4869-08-ac-nullHandling.diff, derby-4869-09-ac-abort.diff, derby-4869-10-aa-abortSecurityTest.diff, derby-4869-11-aa-abortHidePrivates.diff, derby-4869-12-aa-xaAndPooledAborts.diff, derby-4869-13-aa-xaAndPooledAbortsSecurityManager.diff, derby-4869-14-ac-closeOnCompletion.diff, derby-4869-15-aa-autoGenKeys.diff, derby-4869-16-aa-clarifyStatementSpec.diff, derby-4869-17-aa-statementTimeoutException.diff, derby-4869-18-aa-getSetSchema.diff, derby-4869-19-aa-getSetNetworkTimeout.diff, derby-4869-20-aa-setSchemaFastPath.diff, derby-4869-21-aa-implicitlyClosedResultSets.diff, derby-4869-21-ab-implicitlyClosedResultSets.diff, derby-4869-22-aa-unstableStatementTest.diff, derby-4869-23-aa-dbmd.diff, derby-4869-24-ab-getParentLogger.diff, derby-4869-25-aa-removeClosureCheck.diff, derby-4869-26-aa-signatureTests.diff, derby-4869-27-aa-driver40.diff, derby-4869-28-ab-autoloadExceptionFactory.diff, derby-4869-29-aa-fixAutoloadTest.diff, derby-4869-30-aa-unstableStatementTest.diff, derby-4869-31-aa-unstableStatementTest.diff, derby-4869-31-ab-unstableStatementTest.diff, derby-4869-exp-01-aa-noTryCatch.diff, disable-tests.diff, timezone.diff
>
>
> This is a master issue logged to track our work implementing JDBC 4.1, the changes to the java.sql and javax.sql packages introduced by Java 7.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira