[
https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636489#action_12636489
]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
> Do the conglomerate properties fall into this category..?
It seems these can all be changed, but change will not impact existing
conglomerates, only tables or indexes created after the change.
> 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-3.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.
