From derby-dev-return-96214-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Fri Jun 1 14:37:24 2012 Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E1F959FAD for ; Fri, 1 Jun 2012 14:37:23 +0000 (UTC) Received: (qmail 82058 invoked by uid 500); 1 Jun 2012 14:37:23 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82015 invoked by uid 500); 1 Jun 2012 14:37:23 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 81791 invoked by uid 99); 1 Jun 2012 14:37:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2012 14:37:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 68D07141663 for ; Fri, 1 Jun 2012 14:37:23 +0000 (UTC) Date: Fri, 1 Jun 2012 14:37:23 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: <708907930.26819.1338561443431.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1975346544.41924.1320085532606.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (DERBY-5488) Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-5488: --------------------------------- Attachment: derby-5488-11-aa-javadoc.diff Attaching derby-5488-11-aa-javadoc.diff. This adjusts the top level index.html to note that the JDBC 4.1 api should be consulted if you are running on Java 6 or higher. This also makes corresponding changes to the javadoc for the JDBC 4.1 DataSources. Committed at subversion revision 1345197. Ported to 10.9 branch at subversion revision 1345204. Touches the following files: M java/engine/org/apache/derby/jdbc/EmbeddedXADataSource40.java M java/engine/org/apache/derby/jdbc/EmbeddedDataSource40.java M java/engine/org/apache/derby/jdbc/EmbeddedConnectionPoolDataSource40.java M java/client/org/apache/derby/jdbc/ClientXADataSource40.java M java/client/org/apache/derby/jdbc/ClientConnectionPoolDataSource40.java M java/client/org/apache/derby/jdbc/ClientDataSource40.java M index.html > Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc. > ----------------------------------------------------------------------- > > Key: DERBY-5488 > URL: https://issues.apache.org/jira/browse/DERBY-5488 > Project: Derby > Issue Type: Improvement > Components: JDBC, SQL > Affects Versions: 10.9.1.0 > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Fix For: 10.9.1.0 > > Attachments: JDBC_4.1_Supplement.html, derby-5488-01-aa-objectMappingAndConversion.diff, derby-5488-02-aa-fixBigInteger.diff, derby-5488-03-ac-moveDecimalSetterGetterAndTest.diff, derby-5488-04-aa-fixBigIntegerDecimal.diff, derby-5488-05-ad-limitOffset.diff, derby-5488-06-aa-limitOffsetTests.diff, derby-5488-07-aa-booleanObjects.diff, derby-5488-08-aa-extraLimitOffsetTest.diff, derby-5488-09-aa-jdbcMinorVersion.diff, derby-5488-10-aa-metadataTypo.diff, derby-5488-10-ab-metadataTypo.diff, derby-5488-10-ac-metadataTypo.diff, derby-5488-11-aa-javadoc.diff, fix-jdbc30-test.diff, releaseNote.html, z.java > > > In addition to the JDBC 4.1 bits which were visible in the Java 7 javadoc, a couple other items appear in the JDBC 4.1 Maintenance Review spec. This spec has been published on the JCP website at http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-eval-spec/index.html. I will attach a functional spec for the remaining bits. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira