Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14248 invoked from network); 23 Sep 2009 19:05:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Sep 2009 19:05:40 -0000 Received: (qmail 45034 invoked by uid 500); 23 Sep 2009 19:05:40 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 45002 invoked by uid 500); 23 Sep 2009 19:05:40 -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 44991 invoked by uid 99); 23 Sep 2009 19:05:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2009 19:05:40 +0000 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, 23 Sep 2009 19:05:37 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3E010234C4B4 for ; Wed, 23 Sep 2009 12:05:16 -0700 (PDT) Message-ID: <1326122009.1253732716253.JavaMail.jira@brutus> Date: Wed, 23 Sep 2009 12:05:16 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Closed: (DERBY-4377) Developer's Guide statement on shutting down Derby needs qualification In-Reply-To: <1298632770.1253047559504.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase closed DERBY-4377. ---------------------------- Fix appears in latest alpha manuals, so closing. > Developer's Guide statement on shutting down Derby needs qualification > ---------------------------------------------------------------------- > > Key: DERBY-4377 > URL: https://issues.apache.org/jira/browse/DERBY-4377 > Project: Derby > Issue Type: Bug > Components: Documentation > Affects Versions: 10.5.3.0 > Reporter: Kim Haase > Assignee: Kim Haase > Priority: Minor > Fix For: 10.6.0.0 > > Attachments: DERBY-4377-2.diff, DERBY-4377-3.diff, DERBY-4377.diff, tdevdvlp40464.html, tdevdvlp40464.html, tdevdvlp40464.html > > > The topic "Shutting down Derby or an individual database" (http://db.apache.org/derby/docs/dev/devguide/tdevdvlp40464.html) begins, > "Applications in an embedded environment shut down the Derby system by specifying the shutdown=true attribute in the connection URL. To shut down the system, you do not specify a database name, and you must not specify any other attribute." > This statement actually needs some qualification, because (according to Francois Orsini) "if you have defined Derby's BUILT-IN user authentication at the System level (e.g. setting username / password in derby.properties file)" you do need to specify a username and password when you shut down the database. > The topic needs to include this information. Further suggestions on the wording are welcome. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.