db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4869) Implement JDBC 4.1, the api increment introduced by Java 7
Date Thu, 17 Feb 2011 18:27:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995962#comment-12995962
] 

Kathey Marsden commented on DERBY-4869:
---------------------------------------

Thank you Rick. That does clarify things alot.  I did not know there was any autoloader capability
in JDK 1.4.  Do we support that property now? 

 I think where things have gotten hairy with the Autoloader is that, if I am not mistaken,
the AutoloadedDriver loads even with the DataSources and that is why DERBY-2905 became such
an issue for Tomcat users and other app servers that don't use DriverManager at all and then
since DriverManager only loads it the first time, there is some sort of odd incongruity that
I can't quite put into words.  I think that the behavior and the interfaces we have now are
good, but hope with some thought we can find a way to make the code simpler and more intuitive
per Dan's  comment here: https://issues.apache.org/jira/browse/DERBY-2905?focusedCommentId=12537404&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12537404

I really appreciate the clarification of the current model.



> 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

       

Mime
View raw message