Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 24 Mar 2011 18:49:05 +0000 (UTC)
From: "Lily Wei (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1359120322.9134.1300992545736.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <18489786.105421288207880307.JavaMail.jira@thor>
Subject: [jira] [Updated] (DERBY-4869) Implement JDBC 4.1, the api increment
 introduced by Java 7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-4869?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lily Wei updated DERBY-4869:
----------------------------

    Attachment: PSTimeout_execute.java

Thanks, Knut. I can agree that the PSTimeout class is just experience the s=
ame issue as DERBY-4863. How about the case for PSTimeout_execute.java? The=
 ResultSet takes more than 5 seconds to get and the setQuerytimeout is set =
to 5 seconds. The SQLTimeoutException is throwing about 19 to 21 seconds la=
ter. Does Derby throw SQLTimeoutException twice long as the value set to se=
tQueryTimeout? How does user know when SQLTimeoutException get throw depend=
ing on the value they set to setQueryTimeout?

> 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, PSTimeout.java, P=
STimeout_execute.java, 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-ge=
tObject.diff, derby-4869-07-aa-timedisplacement.diff, derby-4869-08-ac-null=
Handling.diff, derby-4869-09-ac-abort.diff, derby-4869-10-aa-abortSecurityT=
est.diff, derby-4869-11-aa-abortHidePrivates.diff, derby-4869-12-aa-xaAndPo=
oledAborts.diff, derby-4869-13-aa-xaAndPooledAbortsSecurityManager.diff, de=
rby-4869-14-ac-closeOnCompletion.diff, derby-4869-15-aa-autoGenKeys.diff, d=
erby-4869-16-aa-clarifyStatementSpec.diff, derby-4869-17-aa-statementTimeou=
tException.diff, derby-4869-18-aa-getSetSchema.diff, derby-4869-19-aa-getSe=
tNetworkTimeout.diff, derby-4869-20-aa-setSchemaFastPath.diff, derby-4869-2=
1-aa-implicitlyClosedResultSets.diff, derby-4869-21-ab-implicitlyClosedResu=
ltSets.diff, derby-4869-22-aa-unstableStatementTest.diff, derby-4869-23-aa-=
dbmd.diff, derby-4869-24-ab-getParentLogger.diff, derby-4869-25-aa-removeCl=
osureCheck.diff, derby-4869-26-aa-signatureTests.diff, derby-4869-27-aa-dri=
ver40.diff, derby-4869-28-ab-autoloadExceptionFactory.diff, derby-4869-29-a=
a-fixAutoloadTest.diff, derby-4869-30-aa-unstableStatementTest.diff, derby-=
4869-31-aa-unstableStatementTest.diff, derby-4869-31-ab-unstableStatementTe=
st.diff, derby-4869-32_add_CallableStatement_Connection_getTypeMap_test.dif=
f, derby-4869-33_add_CallableStatement_Connection_getTypeMap_test.diff, der=
by-4869-exp-01-aa-noTryCatch.diff, disable-tests.diff, fix-compiler-warning=
.diff, timezone.diff
>
>
> This is a master issue logged to track our work implementing JDBC 4.1, th=
e 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