Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 28812 invoked from network); 13 Nov 2008 00:22:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Nov 2008 00:22:05 -0000 Received: (qmail 70726 invoked by uid 500); 13 Nov 2008 00:22:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 70693 invoked by uid 500); 13 Nov 2008 00:22:12 -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 70682 invoked by uid 99); 13 Nov 2008 00:22:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 16:22:12 -0800 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; Thu, 13 Nov 2008 00:21:00 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7542B234C281 for ; Wed, 12 Nov 2008 16:21:44 -0800 (PST) Message-ID: <1304137718.1226535704479.JavaMail.jira@brutus> Date: Wed, 12 Nov 2008 16:21:44 -0800 (PST) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual In-Reply-To: <29510837.1172775230664.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-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647135#action_12647135 ] Dag H. Wanvik commented on DERBY-2389: -------------------------------------- I think the essential semantics should be explained in the reference manual. The precedence information is part of that, in my view. Usually, the developer's guide carries the conceptual information. If it task admin task related, the admin guide is good. +1 to commit and refine later. > DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual > ------------------------------------------------------------------------------------ > > Key: DERBY-2389 > URL: https://issues.apache.org/jira/browse/DERBY-2389 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.4.2.0 > Reporter: Laura Stewart > Assignee: Kim Haase > Attachments: DERBY-2389-adminguide.diff, DERBY-2389-adminguide.stat, DERBY-2389-adminguide.zip, DERBY-2389-devguide.diff, DERBY-2389-devguide.stat, DERBY-2389-devguide.zip, DERBY-2389-getstart.diff, DERBY-2389-getstart.stat, DERBY-2389-getstart.zip, DERBY-2389-ref.diff, DERBY-2389-ref.stat, DERBY-2389-ref.zip, DERBY-2389-ref2.zip, DERBY-2389-tuning.diff, DERBY-2389-tuning.stat, DERBY-2389-tuning.zip > > > From Derby User list: > On 2/21/07, Anders Morken wrote: > > Shooting from the hip here, but one thing that has occured to me a few > > times as I've browsed the docs to figure something out is that I > > intuitively expect Derby system and database properties (especially the > > non-performance-related) to be documented in the reference guide, not > > the tuning guide. =) > On 2/21/07, Oystein Grovlen - Sun Norway wrote: > > I agree on this. I would have preferred that all "facts" where > > presented in the Reference Manual, and that the other manuals where more > > "pedagogical" presentations of the same material. Currently, it is not > > very intuitive to determine which manual has the information you are > > looking for. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.