db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6473) Manuals are inconsistent in subsubprotocol information
Date Thu, 20 Feb 2014 16:31:29 GMT

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

ASF subversion and git services commented on DERBY-6473:

Commit 1570260 from [~chaase3] in branch 'docs/trunk'
[ https://svn.apache.org/r1570260 ]

DERBY-6473  Manuals are inconsistent in subsubprotocol information

Modified 1 Reference Manual topic.

Patch: DERBY-6473-2.diff

> 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
>             Fix For:,
>         Attachments: DERBY-6473-2.diff, 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