Interface COM.odi.ObjectStoreConstants

public interface ObjectStoreConstants
The ObjectStoreConstants interface defines constants that are used throughout the ObjectStore API.


Variable Index

 o ALL_EXECUTE
File mode for all execute permission.
 o ALL_READ
File mode for all read permission.
 o ALL_WRITE
File mode for all write permission.
 o DEFAULT
The database open mode for keeping the same open mode or else using the auto-open mode.
 o DISABLE_AUTO_OPEN
The value to pass to setAutoOpenMode() to disable auto-opening of databases.
 o GROUP_EXECUTE
File mode for group execute permission.
 o GROUP_READ
File mode for group read permission.
 o GROUP_WRITE
File mode for group write permission.
 o INSTALL_SCHEMA_BATCH
Schema installation mode that specifies that schema installation should be done in batch mode (this constant is not used in PSE/PSE Pro).
 o INSTALL_SCHEMA_INCREMENTAL
Schema installation mode that specifies that schema installation should be done in incremental mode (this constant is not used in PSE/PSE Pro).
 o MVCC
The database open mode for multiversion concurrency control (MVCC).
 o OBJECTSTORE
The ObjectStore.whichProduct() method returns this value if you are running the Java interface to ObjectStore.
 o OTHER_EXECUTE
File mode for other execute permission.
 o OTHER_READ
File mode for other read permission.
 o OTHER_WRITE
File mode for other write permission.
 o OWNER_EXECUTE
File mode for owner execute permission.
 o OWNER_READ
File mode for owner read permission.
 o OWNER_WRITE
File mode for owner write permission.
 o PSE
The ObjectStore.whichProduct() method returns this value if you are running ObjectStore PSE.
 o PSE_PRO
The ObjectStore.whichProduct() method returns this value if you are running ObjectStore PSE Pro.
 o READONLY
The type value for a readonly transaction or the database open mode for readonly.
 o READONLY_NON_BLOCKING
Open mode for readonly that does not block processing to wait for the database lock (not valid in OSJI).
 o RETAIN_HOLLOW
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to make persistent objects hollow.
 o RETAIN_READONLY
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to maintain all persistent objects and retain their contents as well.
 o RETAIN_STALE
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to make persistent objects stale.
 o RETAIN_UPDATE
The retain value when calling Transaction.commit(int) or Transaction.abort(int) to maintain all persistent objects, retain their contents, and permit modifications to them between transactions.
 o UPDATE
The type value for an update transaction or the database open mode for update.
 o UPDATE_NON_BLOCKING
Open mode for update that does not block processing to wait for the database lock (not valid for OSJI).
 o WAIT_FOREVER
The timeout value to specify in calls to acquireLock() methods to specify that you want to wait until the lock is available.

Variables

 o PSE
  public final static int PSE
The ObjectStore.whichProduct() method returns this value if you are running ObjectStore PSE.

 o PSE_PRO
  public final static int PSE_PRO
The ObjectStore.whichProduct() method returns this value if you are running ObjectStore PSE Pro.

 o OBJECTSTORE
  public final static int OBJECTSTORE
The ObjectStore.whichProduct() method returns this value if you are running the Java interface to ObjectStore.

 o RETAIN_STALE
  public final static int RETAIN_STALE
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to make persistent objects stale.

 o RETAIN_HOLLOW
  public final static int RETAIN_HOLLOW
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to make persistent objects hollow.

 o RETAIN_READONLY
  public final static int RETAIN_READONLY
The retain value when calling Transaction.abort(int), Transaction.commit(int), ObjectStore.evict(Object, int), or ObjectStore.evictAll(int) to maintain all persistent objects and retain their contents as well.

 o RETAIN_UPDATE
  public final static int RETAIN_UPDATE
The retain value when calling Transaction.commit(int) or Transaction.abort(int) to maintain all persistent objects, retain their contents, and permit modifications to them between transactions.

 o OWNER_READ
  public final static int OWNER_READ
File mode for owner read permission.

See Also:
create
 o OWNER_WRITE
  public final static int OWNER_WRITE
File mode for owner write permission.

See Also:
create
 o OWNER_EXECUTE
  public final static int OWNER_EXECUTE
File mode for owner execute permission.

See Also:
create
 o GROUP_READ
  public final static int GROUP_READ
File mode for group read permission.

See Also:
create
 o GROUP_WRITE
  public final static int GROUP_WRITE
File mode for group write permission.

See Also:
create
 o GROUP_EXECUTE
  public final static int GROUP_EXECUTE
File mode for group execute permission.

See Also:
create
 o OTHER_READ
  public final static int OTHER_READ
File mode for other read permission.

See Also:
create
 o OTHER_WRITE
  public final static int OTHER_WRITE
File mode for other write permission.

See Also:
create
 o OTHER_EXECUTE
  public final static int OTHER_EXECUTE
File mode for other execute permission.

See Also:
create
 o ALL_READ
  public final static int ALL_READ
File mode for all read permission.

See Also:
create
 o ALL_WRITE
  public final static int ALL_WRITE
File mode for all write permission.

See Also:
create
 o ALL_EXECUTE
  public final static int ALL_EXECUTE
File mode for all execute permission.

See Also:
create
 o READONLY
  public final static int READONLY
The type value for a readonly transaction or the database open mode for readonly.

See Also:
begin, open
 o UPDATE
  public final static int UPDATE
The type value for an update transaction or the database open mode for update.

See Also:
begin, open
 o MVCC
  public final static int MVCC
The database open mode for multiversion concurrency control (MVCC).

See Also:
open
 o DEFAULT
  public final static int DEFAULT
The database open mode for keeping the same open mode or else using the auto-open mode.

See Also:
open
 o DISABLE_AUTO_OPEN
  public final static int DISABLE_AUTO_OPEN
The value to pass to setAutoOpenMode() to disable auto-opening of databases.

See Also:
setAutoOpenMode, getAutoOpenMode
 o UPDATE_NON_BLOCKING
  public final static int UPDATE_NON_BLOCKING
Open mode for update that does not block processing to wait for the database lock (not valid for OSJI).

See Also:
open
 o READONLY_NON_BLOCKING
  public final static int READONLY_NON_BLOCKING
Open mode for readonly that does not block processing to wait for the database lock (not valid in OSJI).

See Also:
open
 o WAIT_FOREVER
  public final static int WAIT_FOREVER
The timeout value to specify in calls to acquireLock() methods to specify that you want to wait until the lock is available.

See Also:
acquireLock, acquireLock, acquireLock
 o INSTALL_SCHEMA_BATCH
  public final static int INSTALL_SCHEMA_BATCH
Schema installation mode that specifies that schema installation should be done in batch mode (this constant is not used in PSE/PSE Pro). If a database is created with batch schema installation mode in effect, the application schema database types will be installed immediately into the database schema. This has the effect of reducing the likelihood that a concurrency conflict will occur due to type installation. The disadvantage of this mode is that the database will be significantly larger initially and database creation will take somewhat longer than it would otherwise.

See Also:
create
 o INSTALL_SCHEMA_INCREMENTAL
  public final static int INSTALL_SCHEMA_INCREMENTAL
Schema installation mode that specifies that schema installation should be done in incremental mode (this constant is not used in PSE/PSE Pro). If a database is created with incremental schema installation mode in effect, only a select set of types from the application schema database are initially installed into the database schema. This has the effect of reducing the initial database size and speeding up database creation but increases the likelihood of a concurrency conflict later due to schema installation.

See Also:
create

Copyright © 1996, 1997, 1998 Object Design, Inc. All rights reserved.