[ 
https://issues.apache.org/jira/browse/DERBY-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick Hillegas updated DERBY-4869:
---------------------------------

    Attachment: derby-4869-18-aa-getSetSchema.diff

Attaching derby-4869-18-aa-getSetSchema.diff. This patch implements the new 
JDBC 4.1 methods Connection.getSchema() and Connection.setSchema(). I am 
running regression tests now.

This patch takes advantage of existing shortcuts for getSchema() in both the 
embedded and network cases. The setSchema() method has more error paths so I 
opted for implementing it on top of the SQL layer. We may want to revisit this 
implementation if it causes a performance drag in the wild.



Touches the following files:

-----------

M      java/engine/org/apache/derby/impl/jdbc/EmbedConnection.java
M      java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection.java
M      java/engine/org/apache/derby/iapi/jdbc/EngineConnection.java

Embedded implementation.

-----------


M      java/client/org/apache/derby/client/am/Connection.java
M      java/client/org/apache/derby/client/am/LogicalConnection.java

Network implementation.

-----------

M      
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/Wrapper41Conn.java
M      
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/ConnectionMethodsTest.java

Tests.


> 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: 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-exp-01-aa-noTryCatch.diff, 
> disable-tests.diff, JDBC_4.1_Changes.html, 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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to