db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3847) Tuning Guide lacks information on turning off Derby property settings
Date Thu, 16 Oct 2008 12:02:44 GMT

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

Knut Anders Hatlen commented on DERBY-3847:
-------------------------------------------

For a system-wide, dynamic property set in derby.properties, I don't
think it is correct that it persists until the value is changed or the
file is removed. At least, that's not what I observed when I tried to
change derby.locks.waitTimeout (which is system-wide and dynamic
according to the documentation). So I think you need to add "and the
system is rebooted", like you did for the static properties.

See also http://db.apache.org/derby/docs/dev/tuning/ctunsetprop44147.html:

> Note: Properties set in the derby.properties file and on the command
> line of the application that boots Derby are always static, because
> Derby reads this file and those parameters only at startup.

> 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