Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 71128 invoked from network); 25 May 2007 16:38:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 May 2007 16:38:37 -0000 Received: (qmail 88005 invoked by uid 500); 25 May 2007 16:38:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87982 invoked by uid 500); 25 May 2007 16:38: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 87969 invoked by uid 99); 25 May 2007 16:38:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2007 09:38: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; Fri, 25 May 2007 09:38:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5D57E714065 for ; Fri, 25 May 2007 09:38:16 -0700 (PDT) Message-ID: <1244837.1180111096379.JavaMail.jira@brutus> Date: Fri, 25 May 2007 09:38:16 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2654) Document newly-supported (in embedded mode) JDBC methods for autogenerated keys. In-Reply-To: <5997207.1179251116177.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-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499150 ] Kim Haase commented on DERBY-2654: ---------------------------------- Thanks, Army! I will make the first two fixes. The third is an interesting problem. If you look at http://db.apache.org/derby/docs/dev/ref/, you can see that the "Autogenerated keys" topic is actually a subtopic under the "java.sql.Statement interface: supported JDBC 3.0 methods" topic. This means that in this topic, the "Autogenerated keys" topic is automatically placed in a bullet list by the DITA processor. But for other topics that need to refer to it I need to create a reference. I could try to make it look like the one under Statement, but I'm not sure I could duplicate this exactly. The other option is to make it a subsection at the same level as the other JDBC 3.0 topics. This can be done just by fiddling with the map file. I think in that case it would show up in the Related Reference list along with the other topics in this part of the hierarchy. Would that be preferable? > Document newly-supported (in embedded mode) JDBC methods for autogenerated keys. > -------------------------------------------------------------------------------- > > Key: DERBY-2654 > URL: https://issues.apache.org/jira/browse/DERBY-2654 > Project: Derby > Issue Type: Sub-task > Components: Documentation > Affects Versions: 10.3.0.0 > Reporter: A B > Assigned To: Kim Haase > Attachments: changes.txt, changes.txt, DERBY-2654.diff, DERBY-2654.zip > > > Several JDBC methods for specifying auto-generated key columns were implemented in embedded mode as part of DERBY-2631. Derby documentation should be updated to reflect those changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.