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-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual
Date Tue, 26 Aug 2008 15:26:44 GMT

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

Kim Haase commented on DERBY-2389:
----------------------------------

I've been working through these and have run into some technical questions on tuning guide
topics.

http://db.apache.org/derby/docs/dev/tuning/rtunproper27529.html (derby.storage.initialPages):
The topic does not say whether the property is dynamic or static. The table of properties
(ctunproper22250.html) implies that it is static (there is no X for dynamic). However, this
is the only property that applies only to conglomerates (not system or database). Is the static/dynamic
distinction relevant?

http://db.apache.org/derby/docs/dev/tuning/rtunproper81359.html (derby.storage.pageCacheSize):
There's a paragraph referring to an ancient JVM (1.1.7) and OS (Windows NT). Is it possible
to update this (i.e. do we have a valid suggestion for current software) or should it just
be removed?

http://db.apache.org/derby/docs/dev/tuning/ctunsetprop824451.html (Scope of properties, under
"Working with Derby properties" at the beginning of the Tuning Guide) describes the conglomerate-specific
scope in addition to system-wide and database-wide. http://db.apache.org/derby/docs/dev/tuning/ctunproper51399.html
(Scope of Derby properties), in the reference section that's being moved to the Reference
Manual, mentions only the system-wide and database-wide scopes. Should the conglomerate-specific
scope be added to ctunproper51399.html?

I'll be very grateful for advice on these.


> 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
>            Reporter: Laura Stewart
>            Assignee: Kim Haase
>
> 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