db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2182) Documentation for derby.system.bootAll is missing
Date Fri, 30 Nov 2007 19:54:43 GMT

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

Kim Haase commented on DERBY-2182:

That's a very good point, Dan. Since the IBM docs are the only source of information on these
properties, we really cannot document them without violating that copyright.

This fact, plus the fact that no one has been able to confirm whether or not these properties
work as described, leads me to think that we should NOT add documentation for these properties
to the Tuning Guide, but instead should remove any mention of them from other manuals (mainly
the Developer's Guide). Specifically:

1) Remove the following paragraph from http://db.apache.org/derby/docs/dev/devguide/cdevdvlp27715.html:

You can also configure your system to automatically boot all databases in the system when
it starts up; see derby.system.bootAll in the Tuning Derby manual. Because of the time needed
to boot a database, the number of databases in the system directory affects startup performance
if you use that configuration.

2) Change the following paragraph in http://db.apache.org/derby/docs/dev/devguide/cdevcsecure60146.html

Encrypted databases cannot be booted automatically along with all other system databases on
system startup (see "derby.system.bootAll"  in Tuning Derby). Instead, you boot encrypted
databases when you first connect to the database.


You boot encrypted databases when you first connect to the database.

3) Change the following paragraph in http://db.apache.org/derby/docs/dev/devguide/cdevadvjdbc41138.html

Databases in a system are not automatically booted until you connect with them. You can configure
your system to retain the former behavior, in which case the steps described in this section
will continue to work. See "derby.system.bootAll"  in Tuning Derby.


Databases in a system are not automatically booted until you connect with them. 

4) Possibly remove the topic http://db.apache.org/derby/docs/dev/tuning/ctunperf16556.html,
whose text is below. If there is no way to boot databases at startup, this topic has no purpose.
It doesn't actually say *how* to boot databases at startup, though the bootAll and noAutoBoot
properties both have index entries. Is there any other way?

By default, Derby does not boot databases (and some core Derby classes) in the system at Derby
startup but only at connection time. For multi-user systems, you might want to reduce connection
time by booting one or all databases at startup instead.

For embedded systems, you might want to boot the database in a separate thread (either as
part of the startup, or in a connection request).

For more information, see Shielding users from Derby class-loading events.

Would this make more sense? If so, I'll file a patch to do this.

> 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.

View raw message