background image
<< derby.database.forceDatabaseLock | derby.database.readOnlyAccessUsers >>

derby.database.noAutoBoot

<< derby.database.forceDatabaseLock | derby.database.readOnlyAccessUsers >>
Derby Reference Manual
365
Note: User names, called authorization identifiers, follow the rules of SQL92Identifiers
and can be delimited. Specifying a user name that does not follow these rules raises an
exception.
For more information about user authorization, see "User Authorization" in the Derby
Developer's Guide
.
Syntax
-- database-level property
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.fullAccessUsers',
'commaSeparatedlistOfUsers')
Example
-- database-level property
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.fullAccessUsers', 'dba,fred,peter')
--system-level property
derby.database.fullAccessUsers=dba,fred,peter
Dynamic or static
Dynamic. Current connections are not affected, but all future connections are affected.
For information about dynamic changes to properties, see
Dynamic and static properties
.
derby.database.noAutoBoot
Function
Specifies that a database should not be automatically booted at startup time.
When this property is set to true, this database is booted only on the first connection.
Otherwise, the database is booted at startup if the derby.system.bootAll property is set to
true. See
derby.system.bootAll
for details.
Default
False.
Example
-- database-level property
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
'derby.database.noAutoBoot', 'true')
Scope
database-wide
Dynamic or static
This property is static; if you change it while Derby is running, the change does not take
effect until you reboot.
derby.database.propertiesOnly
Function
When set to true, this property ensures that database-wide properties cannot be
overridden by system-wide properties.
When this property is set to false, or not set, database-wide properties can be overridden
by system-wide properties (see "Precedence of properties" in the Derby Developer's
Guide
).