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 Thu, 05 Mar 2009 18:35:57 GMT

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

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

Dag, you asked, about http://db.apache.org/derby/docs/dev/devguide/cdevsetprop12821.html:

   - "If you specify an invalid value, Derby uses the default value for
      the property."

      So, if a subsequent SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY is
      called, does it return the default or the non-valid value set?

      The reference manual section doesn't explain this either:
      http://db.apache.org/derby/docs/dev/ref/rrefsetdbpropproc.html 

A limited experiment (using derby.connection.requireAuthentication, derby.authentication.provider,
and derby.storage.initialPages) suggests the following:

At the beginning, if a property is not set at all, SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY
returns "null", but appears to use the default value. If you then set the property to an invalid
value, SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY returns the invalid value, but appears to use
the default value as before.

I should probably edit http://db.apache.org/derby/docs/dev/ref/rrefsetdbpropproc.html and
probably http://db.apache.org/derby/docs/dev/ref/rrefgetdbpropfunc.html to mention this, as
well as http://db.apache.org/derby/docs/dev/devguide/cdevsetprop12821.html.


> 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-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