db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual
Date Thu, 19 Mar 2009 22:25:50 GMT

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

Dag H. Wanvik commented on DERBY-2389:
--------------------------------------

Thanks for the latest sets of fixes (phase3), Kim!

Some final comments; feel free to commit and close this issue now!

* cdevsetprop13074.dita

> There should be one derby.properties file per system, not one per database.

Suggest:

   There is one one derby.properties ...

* cdevsetprop24843.dita

> Programmatically (as a command-line option to the JVM when starting
> the application or within application code)

This is misleading, since the application is normally the client side.

Suggest:

    (as a command line option when starting the JVM that holds
    the server or, if the server is started from with a program,
    programmatically by the program which hosts the server)

* cdevsetprop824451.dita

> Database-wide properties are stored in the database and are simpler for deployment.

Suggest:

    Database-wide properties are stored in the database and are simpler
    for deployment, in the sense that they follow they
    database. Database-wide properties are also recommended for security
    reasons when Derby built-in authentication is used, cf ...

* cdevsetprop12821.dita

> You should use database-wide properties wherever possible for ease of deployment.

Suggest adding a final:

    ".. and security"

* crefproper51399.dita

> Note: Database-wide properties are stored in the database and are simpler for deployment.


Suggest:

    Note: Database-wide properties are stored in the database and are
    simpler and safer for deployment.



> DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-2389
>                 URL: https://issues.apache.org/jira/browse/DERBY-2389
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.4.2.0
>            Reporter: Laura Stewart
>            Assignee: Kim Haase
>         Attachments: DERBY-2389-adminguide.diff, DERBY-2389-adminguide.stat, DERBY-2389-adminguide.zip,
DERBY-2389-devguide.diff, DERBY-2389-devguide.stat, DERBY-2389-devguide.zip, DERBY-2389-getstart.diff,
DERBY-2389-getstart.stat, DERBY-2389-getstart.zip, DERBY-2389-phase2.diff, DERBY-2389-phase2.stat,
DERBY-2389-phase2.zip, DERBY-2389-phase3.diff, DERBY-2389-phase3.stat, DERBY-2389-phase3.zip,
DERBY-2389-ref.diff, DERBY-2389-ref.stat, DERBY-2389-ref.zip, DERBY-2389-ref2.zip, DERBY-2389-tuning.diff,
DERBY-2389-tuning.stat, DERBY-2389-tuning.zip, derbydev.pdf, tuningderby.pdf
>
>
> From Derby User list:
> On 2/21/07, Anders Morken <andersmo@stud.ntnu.no> wrote:
> > Shooting from the hip here, but one thing that has occured to me a few
> > times as I've browsed the docs to figure something out is that I
> > intuitively expect Derby system and database properties (especially the
> > non-performance-related) to be documented in the reference guide, not
> > the tuning guide. =)
> On 2/21/07, Oystein Grovlen - Sun Norway <Oystein.Grovlen@sun.com> wrote:
> > I agree on this.  I would have preferred that all "facts" where
> > presented in the Reference Manual, and that the other manuals where more
> > "pedagogical" presentations of the same material.  Currently, it is not
> > very intuitive to determine which manual has the information you are
> > looking for.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message