Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14277 invoked from network); 16 Apr 2007 19:11:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Apr 2007 19:11:37 -0000 Received: (qmail 69376 invoked by uid 500); 16 Apr 2007 19:11:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69350 invoked by uid 500); 16 Apr 2007 19:11:42 -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 69338 invoked by uid 99); 16 Apr 2007 19:11:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2007 12:11:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2007 12:11:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 825CA714075 for ; Mon, 16 Apr 2007 12:11:15 -0700 (PDT) Message-ID: <20418688.1176750675531.JavaMail.jira@brutus> Date: Mon, 16 Apr 2007 12:11:15 -0700 (PDT) From: "A B (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource. In-Reply-To: <29355306.1176242132256.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489198 ] A B commented on DERBY-2538: ---------------------------- The version 4 changes look good to me. +1 to commit pending resolution of DERBY-2488. Thank you for addressing this so quickly, Kim! > Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource. > ----------------------------------------------------------------------------------------------------- > > Key: DERBY-2538 > URL: https://issues.apache.org/jira/browse/DERBY-2538 > Project: Derby > Issue Type: Sub-task > Components: Documentation > Affects Versions: 10.2.2.0, 10.3.0.0 > Reporter: A B > Assigned To: Kim Haase > Priority: Minor > Attachments: cdevresman89722.html, DERBY-2538-2.diff, DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff, DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html > > > Based on discussion from DERBY-2488, pages in the Developer's Guide should be improved to describe what happens if a JDBC 4 application uses an "old" (JDBC 3) datasource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.