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-6473) Manuals are inconsistent in subsubprotocol information
Date Thu, 20 Feb 2014 13:56:19 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906962#comment-13906962

Kim Haase commented on DERBY-6473:

Thanks, Myrna -- yes, I agree about the pluses and minuses of losing those links. Wish we
could get xrefs between manuals to work. 

Thanks for noticing that case inconsistency. I will commit this patch and then fix that in
a second patch.

> Manuals are inconsistent in subsubprotocol information
> ------------------------------------------------------
>                 Key: DERBY-6473
>                 URL: https://issues.apache.org/jira/browse/DERBY-6473
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6473.diff, DERBY-6473.stat, DERBY-6473.zip
> Four subsubprotocols are listed in http://db.apache.org/derby/docs/10.10/devguide/cdevdvlp17453.html
(Derby JDBC database connection URL), but only three in http://db.apache.org/derby/docs/10.10/ref/rrefjdbc37352.html
(Syntax of database connection URLs for applications with embedded databases), which was apparently
not updated when we documented in-memory databases. The Reference Manual should be corrected.
> Since reference information really belongs in the Reference Manual and duplicate information
is hard to maintain, it would probably be a good idea to correct the syntax information in
the reference manual topic, remove it from the Developer's Guide topic, and point Developer's
Guide readers to the Reference Manual. I'll plan on doing this unless I hear otherwise.

This message was sent by Atlassian JIRA

View raw message