Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 10372 invoked from network); 3 Sep 2008 16:48:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Sep 2008 16:48:35 -0000 Received: (qmail 55468 invoked by uid 500); 3 Sep 2008 16:48:33 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 55441 invoked by uid 500); 3 Sep 2008 16:48:33 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 55429 invoked by uid 99); 3 Sep 2008 16:48:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2008 09:48:33 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2008 16:47:43 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8DB2C234C1C6 for ; Wed, 3 Sep 2008 09:47:44 -0700 (PDT) Message-ID: <1516249833.1220460464579.JavaMail.jira@brutus> Date: Wed, 3 Sep 2008 09:47:44 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3847) Tuning Guide lacks information on turning off Derby property settings In-Reply-To: <829044681.1219431646871.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on 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.