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-3847) Tuning Guide lacks information on turning off Derby property settings
Date Tue, 07 Oct 2008 17:34:44 GMT

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

Kim Haase commented on DERBY-3847:
----------------------------------

Thanks again, Dag. I am tempted to try to make this right, but you may be right that things
are just too baroque -- too many possibilities. Would it be correct to modify the last part
of http://db.apache.org/derby/docs/dev/tuning/ctunsetprop824500.html to say:

A system-wide property might have persistence, depending on how you set it and whether it
is dynamic or static. If you set it programmatically, it persists only for the duration of
the JVM of the application that set it. If you set it in the derby.properties file, a dynamic
property persists until:

    * That value is changed
    * The file is removed from the system
    * The database is booted outside of that system

A static property set in the derby.properties file persists until:

    * That value is changed and the system is rebooted
    * The file is removed from the system and the system is rebooted
    * The database is booted outside of that system


> Tuning Guide lacks information on turning off Derby property settings
> ---------------------------------------------------------------------
>
>                 Key: DERBY-3847
>                 URL: https://issues.apache.org/jira/browse/DERBY-3847
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.4.1.3
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: ctunproper22250.html, ctunproper22250.html, DERBY-3847-2.diff, DERBY-3847-2.zip,
DERBY-3847-3.diff, DERBY-3847-4.diff, DERBY-3847.diff, DERBY-3847.stat, DERBY-3847.zip
>
>
> The documentation of how to turn off Derby properties is spotty. Dag Wanvik reports that
"I checked the code, and when you set a database property to a null value, that property is
removed from the list of database properties; i.e. the situation is back to where you were
before it was first set, so the built-in defaults apply again (or system properties if there
are any)."
> The behavior for turning off user settings is slightly different and is documented in
several places; it's the general case that seems to be missing. This information needs to
be added to the description of Derby properties in the Tuning Guide, probably in the general
topic "Derby properties" (http://db.apache.org/derby/docs/dev/tuning/ctunproper22250.html).

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