db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2654) Document newly-supported (in embedded mode) JDBC methods for autogenerated keys.
Date Fri, 25 May 2007 16:38:16 GMT

    [ 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:
>            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.

View raw message