You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2008/08/22 21:00:46 UTC
[jira] Created: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
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
Priority: Minor
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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627000#action_12627000 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
Ah yes, sigh.. this is really confusing.
> So I guess if you had previously set a system-wide property
> programmatically, then set it database-wide, then set the
> database-wide version to null, the previous programmatic system-wide
> setting would take effect.
Yes, that was what I was thinking of.
> If there was none, the default for the
> database-wide property would take effect. Or would it? Would you
> then slip down to the derby.properties file setting if there was
> one?
Looking at the code in PropertyUtil.java it would then slip down to
derby.properties (cf. logic in getPropertyFromSet), correct.
> There's also the fact that some properties have *only* system scope
or only database scope.
As far as I can tell, this is orthogonal to how the value is
established. I think it is good to explain all these intricacies in one place.
> 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.diff
>
>
> 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Derby Info: [Patch Available]
> 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, DERBY-3847.diff
>
>
> 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.
[jira] Assigned: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-3847:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625755#action_12625755 ]
Kim Haase commented on DERBY-3847:
----------------------------------
Hmm -- actually it may be even more confusing because according to the "Precedence of properties" topic of the tuning guide,
The search order for properties is:
1. System-wide properties set programmatically (as a command-line option to the JVM when starting the application or within application code)
2. Database-wide properties
3. System-wide properties set in the derby.properties file
So I guess if you had previously set a system-wide property programmatically, then set it database-wide, then set the database-wide version to null, the previous programmatic system-wide setting would take effect. If there was none, the default for the database-wide property would take effect. Or would it? Would you then slip down to the derby.properties file setting if there was one?
There's also the fact that some properties have *only* system scope or only database scope.
Maybe rather than try to describe all the permutations, we should just refer readers to the "Working with Derby properties" section of the tuning guide (which will actually stay in the tuning guide rather than be moved over to the Reference Manual when DERBY-2389 is done). What do you think?
> 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.diff
>
>
> 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Attachment: DERBY-3847-3.zip
DERBY-3847-5.diff
Thanks again, Knut and Dag, for catching this. I have updated ctunsetprop824500.html to remove the distinction between dynamic and static properties set in derby.properties -- since these are always static. Hope this works.
Attaching DERBY-3847-5.diff and DERBY-3847-3.zip with this fix.
> 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-3.zip, DERBY-3847-4.diff, DERBY-3847-5.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.
[jira] Closed: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-3847.
----------------------------
Closing, since fixes have appeared in the Latest Alpha Docs.
> 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
> Fix For: 10.5.0.0
>
> Attachments: ctunproper22250.html, ctunproper22250.html, DERBY-3847-2.diff, DERBY-3847-2.zip, DERBY-3847-3.diff, DERBY-3847-3.zip, DERBY-3847-4.diff, DERBY-3847-5.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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625413#action_12625413 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
Thanks for fixing this Kim!
You may want to make explicit that when programmatically resetting a property to null, for static properties, you need to reboot the database for the change to have effect (similar tp the case when setting it the first time).
> 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, DERBY-3847.diff
>
>
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636711#action_12636711 ]
Kim Haase commented on DERBY-3847:
----------------------------------
Thanks, Dag, that helps a lot. I have incorporated your suggestions.
About
* "be sure to trim extra spaces around the word true"
Is anything except the exact string "true" treated as meaning "false"? In that case, extra spaces around "false" would not be a problem -- " false " would mean the same thing as "false", though not for the reason the user thinks.
I don't know of any property other than derby.database.sqlAuthorization that can't be disabled once enabled, so I will document that as the only one unless I hear otherwise.
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636485#action_12636485 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
Hi Kim, thanks for the new patch version. I have a couple of small comments:
ctunproper22250.dita:
* As it now stands, it looks kind of weird that the section starts by
explaining how you can *turn off* properties. I think we should first
explain, or point to where it is explained, how to turn them on first?
> (A system property set programmatically takes precedence over a
> system property set in the derby.properties file.)
I think it would be clearer (at the expense of verbosity)
to explicitly list the search order again
before trying to explain how this would work, e.g. some such:
To disable or turn off a database-wide property setting, set its value
to null. What value applies after this is done? To answer that,
recall that the search order is (ref to where explained first time?):
1. [*] System-wide properties set programmatically (as a command-line
option to the JVM when starting the application or within application
code)
2. Database-wide properties
3. [*] System-wide properties set in the derby.properties file
[*] Not consulted if derby.database.propertiesOnly is set to true.
Assuming we are *not* using programmatically set system properties,
setting the database-wide property to null has the effect of removing
the property from the list of database properties and restoring the
system property setting from derby.properties if there is one. As always, if no
value can be determined from the search, the builtin default applies.
* "be sure to trim extra spaces around the word true"
true or false, as the case may be
* Some static properties can not be disabled once enabled, even with a reboot,
notably derby.database.sqlAuthorization. I think this applies for some others as well,
have you seen any list of those? Do the conglomerate properties fall into this category..?
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640192#action_12640192 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
Re Knut's comment: That's my understanding also: derby.properties is not continually being re-read
when it changes.
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642163#action_12642163 ]
Knut Anders Hatlen commented on DERBY-3847:
-------------------------------------------
The latest patch looks clear and correct to me. +1 to commit.
> 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-3.zip, DERBY-3847-4.diff, DERBY-3847-5.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.
[jira] Resolved: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-3847.
------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Derby Info: (was: [Patch Available])
Thanks again, Knut.
Committed patch DERBY-3847-5.diff to documentation trunk at revision 708179.
> 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
> Fix For: 10.5.0.0
>
> Attachments: ctunproper22250.html, ctunproper22250.html, DERBY-3847-2.diff, DERBY-3847-2.zip, DERBY-3847-3.diff, DERBY-3847-3.zip, DERBY-3847-4.diff, DERBY-3847-5.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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Attachment: DERBY-3847.zip
DERBY-3847.stat
DERBY-3847-3.diff
Thanks, Dag.
Actually, the intricacies are explained in one place, more or less -- in the "Working with Derby properties" section of the tuning guide. I think it may make sense to put the information on what happens when you turn off a property in the "Persistence of properties" topic, as well as in the "Derby properties" topic, which will be moving to the Reference Manual. There can be a bit less detail in "Persistence of properties" because there is more context.
I still don't have a lot of confidence in ctunproper22250.dita, so please let me know if further fixes are needed or if what's in the "Working with Derby properties" section will cover us.
I also found a typo at the end of "Derby properties" (a book title with an extra word).
I'm attaching DERBY-3847-3.diff, DERBY-3847.stat, and DERBY-3847.zip.
> 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Attachment: ctunproper22250.html
DERBY-3847.diff
I'm attaching DERBY-3847.diff and ctunproper22250.html.
Please check the language here: I gathered from what Dag said that turning off properties applies at the database-wide level. (I'm not sure it would have any meaning at the system level.)
I also discovered when comparing the table here with the actual property topics that there was no table entry for derby.database.sqlAuthorization, so I've added one. It is a static property.
> 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, DERBY-3847.diff
>
>
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635762#action_12635762 ]
Kim Haase commented on DERBY-3847:
----------------------------------
I plan to commit the latest patch in one week (10/7) unless I hear that further changes are needed. Thanks.
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625603#action_12625603 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
ctunproper22250.html:
> restoring the built-in default setting or the default system property setting, if any.
I think the latter half of this sentence is not very precise: system properties by default
override database level settings (unless derby.database.propertiesOnly has been set).
So, if there is a system level property set and derby.database.propertiesOnly is not set, unsetting
the database level property would not have any effect.
> 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.diff
>
>
> 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.
[jira] Commented: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637265#action_12637265 ]
Dag H. Wanvik commented on DERBY-3847:
--------------------------------------
Thanks for the new patch, Kim! Looks good!
Re "true"/"false"; checking Boolean.valueOf(String) - which Derby uses - it says:
public static Boolean valueOf(String s)
Returns a Boolean with a value represented by the specified string.
The Boolean returned represents a true value if the string argument is not null and is equal,
ignoring case, to the string "true".
So I guess you can keep the current wording :)
Reading "Persistence of properties" again, I get fuzzy (feel free to ignore :-)
> :
> Typically, it is in effect until you
> explicitly change the property or until you set a system-wide property
> with precedence over database-wide properties (see Precedence of
> properties).
The last sentence is perhaps a bit troublesome; it can lead a user into
believing a system-wide property always takes presedence over a
database-wide property, whereas this depends on how it has been set.
Not sure how to phrase it better, though :)
> If you set it in the derby.properties file, a property persists
> until:
> - That value is changed
(if dynamic; if static until system is rebooted)
> - The file is removed from the system
(if dynamic; if static until system is rebooted)
Not sure you can actually remove derby.properties when the VM is running, though;
it may be OS dependent..
> 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Attachment: ctunproper22250.html
DERBY-3847-2.diff
That's a good suggestion, Dag. I've added that information to the topic in DERBY-3847-2.diff and an updated version of ctunproper22250.html. Please let me know how this looks.
Thanks very much!
> 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.diff
>
>
> 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.
[jira] Updated: (DERBY-3847) Tuning Guide lacks information on
turning off Derby property settings
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-3847:
-----------------------------
Attachment: DERBY-3847-2.zip
DERBY-3847-4.diff
Attaching DERBY-3847-4.diff and DERBY-3847-2.zip, with the latest comments incorporated.
> 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.