storeIsMemory

public boolean storeIsMemory

Sets whether tables are to be located in-memory or on disk.
Creating in-memory tables should append "STORE MEMORY" to the
"CREATE TABLE" statement. Creating disk-based tables should
append "STORE DISK". Since cursor hold over commit can not apply
to M-tables (which will cause SOLID Table Error 13187: The cursor
cannot continue accessing M-tables after the transaction has committed
or aborted. The statement must be re-executed.), the default is
STORE DISK.
The default concurrency control mechanism depends on the table type:
Disk-based tables (D-tables) are by default optimistic.
Main-memory tables (M-tables) are always pessimistic.
Since OpenJPA applications expects lock waits (as usually is done with
normal pessimistic databases), the server should be set to the pessimistic mode.
The optimistic mode is about not waiting for the locks at all. That increases
concurrency but requires more programming. The pessimistic mode with the
READ COMMITTED isolation level (default) should get as much concurrency as one
might need. The pessimistic locking mode can be set in solid.ini:
[General]
Pessimistic=yes

useTriggersForAutoAssign

public boolean useTriggersForAutoAssign

If true, then simulate auto-assigned values in SolidDB by
using a trigger that inserts a sequence value into the
primary key value when a row is inserted.

isSystemIndex

This method is used to filter system indexes from database metadata.
Return true if the given index name represents a system index that
should not appear in the schema definition. Returns false by default.

isSystemSequence

This method is used to filter system sequences from database metadata.
Return true if the given sequence represents a system sequence that
should not appear in the schema definition. Returns true if system
schema by default.

isFatalException

Determine if the given SQL Exception is fatal or recoverable (such as a timeout).
This implementation always returns true (i.e. all exceptions are fatal).
The current dictionary implementation can overwrite this method to mark certain
exception conditions as recoverable error.