Interface IDBStore.Props
- Enclosing interface:
IDBStore
DB store properties.- Since:
- 4.0
- Author:
- Eike Stepper
- No Implement
- This interface is not intended to be implemented by clients.
- No Extend
- This interface is not intended to be extended by clients.
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringMaximum number of pending parameter sets across the current DB commit write.static final StringMaximum number of pending parameter sets per JDBC batch statement.static final StringPeriod at which to execute an SQL statement to keep DB connection alive, in minutes.static final StringNumber of additional attempts to connect to the DB after initial connection failure.static final StringNumber of seconds to wait before additional attempts to connect to the DB after initial connection failure.static final StringWhether to create the schema with the specifiednameat startup time, if it does not exist.static final StringWhether to disable the SQL query handler.static final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringMaximum number of ObjectType rows considered by one prequery and ObjectType insert batch.static final StringObjectType duplicate handling mode:SAFEorFAIL.static final StringWhether to qualify table names with theschema name.static final Stringstatic final StringThe name of the DB schema to use for the repository.static final Stringstatic final StringWhether to store packages as zipped byte arrays in the database.
-
Field Details
-
SCHEMA_NAME
The name of the DB schema to use for the repository. If omitted thedefault schema nameof the repository'sDB adapteris used as the schema name.- Since:
- 4.13
- See Also:
-
PREPEND_SCHEMA_NAME
Whether to qualify table names with theschema name.- Since:
- 4.13
- See Also:
-
CREATE_SCHEMA_IF_NEEDED
Whether to create the schema with the specifiednameat startup time, if it does not exist.- Since:
- 4.13
- See Also:
-
CONNECTION_KEEPALIVE_PERIOD
Period at which to execute an SQL statement to keep DB connection alive, in minutes.- See Also:
-
BATCH_STATEMENT_SIZE
Maximum number of pending parameter sets per JDBC batch statement. If absent, the legacyorg.eclipse.emf.cdo.server.db.LIST_BATCH_SIZEproperty is used as the default.- Since:
- 4.15
- See Also:
-
OBJECT_TYPE_BATCH_SIZE
Maximum number of ObjectType rows considered by one prequery and ObjectType insert batch.If omitted,
BATCH_STATEMENT_SIZEand its legacy fallback behavior determine the size.- Since:
- 4.15
- See Also:
-
OBJECT_TYPE_DUPLICATE_POLICY
ObjectType duplicate handling mode:SAFEorFAIL. SAFE is the default and preserves duplicate detection and replay. FAIL skips those safeguards and requires all committed IDs to be fresh. FAIL is suitable only when the operator guarantees that commits cannot introduce already-persistent IDs; use SAFE for merge, import, backup, clone, and other external-permanent-ID scenarios.- Since:
- 4.15
- See Also:
-
BATCH_COMMIT_SIZE
Maximum number of pending parameter sets across the current DB commit write.- Since:
- 4.15
- See Also:
-
CONNECTION_RETRY_COUNT
Number of additional attempts to connect to the DB after initial connection failure.- Since:
- 4.12
- See Also:
-
CONNECTION_RETRY_SECONDS
Number of seconds to wait before additional attempts to connect to the DB after initial connection failure.- Since:
- 4.12
- See Also:
-
ID_COLUMN_LENGTH
- Since:
- 4.2
- See Also:
-
READER_POOL_CAPACITY
- Since:
- 4.2
- See Also:
-
WRITER_POOL_CAPACITY
- Since:
- 4.2
- See Also:
-
FIELD_CONSTRUCTION_TRACKING
- Since:
- 4.3
- See Also:
-
DROP_ALL_DATA_ON_ACTIVATE
- Since:
- 4.4
- See Also:
-
JDBC_FETCH_SIZE
- Since:
- 4.4
- See Also:
-
ZIP_PACKAGE_BYTES
Whether to store packages as zipped byte arrays in the database.When set to
true, packages are stored as zipped byte arrays. This saves database space, but makes it harder to inspect the stored packages outside of CDO.When set to
false(the default), packages are stored as plain XML/XMI.The default value is determined by the "org.eclipse.emf.cdo.server.internal.db.MetaDataManager.ZIP_PACKAGE_BYTES" system property, which defaults to
true.Note: This property only affects newly stored packages. Existing packages are not converted.
- Since:
- 4.14
- See Also:
-
DISABLE_SQL_QUERY_HANDLER
Whether to disable the SQL query handler.When set to
true, the SQL query handler is disabled. This means that clients cannot execute arbitrary SQL queries against the database.When set to
false(the default), the SQL query handler is enabled.The default value is determined by the "org.eclipse.emf.cdo.server.db.DEFAULT_DISABLE_SQL_QUERY_HANDLER" system property, which defaults to
false.- Since:
- 4.15
- See Also:
-