[jira] Issue Comment Edited: (DERBY-2182) Documentation for derby.system.bootAll is missing

["Dag H. Wanvik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550650 ] 

dagw edited comment on DERBY-2182 at 12/11/07 9:36 AM:
----------------------------------------------------------------

> In my experience I don't need to set derby.system.home explicitly if
> the databases to be booted are in the directory from which I start the
> network server. Does that make sense?

In the normal case (boot the database when required), yes. But with
derby.system.bootAll=true, I find that an explicit setting of
derby.system.home is required for the databases in the current
directory to be auto-booted, i.e. once the Derby engine is booted (not
only network server from command line; it applies whenever the engine
is booted as far as I can see).

Are you seeing autoboot of databases in current directory happen even
if derby.system.home is *not* set explicitly? I am not able to
reproduce that...


      was (Author: dagw):
    > In my experience I don't need to set derby.system.home explicitly if
> the databases to be booted are in the directory from which I start the
> network server. Does that make sense?

In the normal case (boot the database when required), yes. But with
derby.system.bootAll=true, I find that an explicit setting of
derby.system.home is required for the databases in the current
directory to be auto-booted, i.e. once the Derby engine is booted (not
only network server from command line; it applies whenever the engine
is booted as far as I can see).

Are you seeing autoboot happen even if derby.system.home is *not* set
explicitly? I am not able to reproduce that...

  
> Documentation for derby.system.bootAll is missing
> -------------------------------------------------
>
>                 Key: DERBY-2182
>                 URL: https://issues.apache.org/jira/browse/DERBY-2182
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-2182.diff, DERBY-2182.stat, DERBY-2182.zip
>
>
> This property is not documented in the Tuning Derby guide, but it is referred to 
> in the developer's guide in a couple of places with dangling pointers to the Tuning Guide:
> http://db.apache.org/derby/docs/dev/devguide/cdevdvlp27715.html
> http://db.apache.org/derby/docs/dev/devguide/cdevcsecure60146.html
> http://db.apache.org/derby/docs/dev/devguide/cdevadvjdbc41138.html
> Googling, I find it documented in older Cloudscape docs e.g. in
> http://www.novell.com/documentation/extendas37/docs/help/java/jdkee/cloudscape/doc/html/coredocs/proper42.htm#1014327,
> but not in Cloudscape 10 docs, e.g. http://publib.boulder.ibm.com/infocenter/cldscp10/topic/com.ibm.cloudscape.doc/perf63.htm
> which could indicate it was removed for some reason. So, either we
> should document it anew or remove the references to it. If we decide to keep it, we should also consider
> derby.database.noAutoBoot (not currently documented).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.