ToC path:

eXtremeSQL Java Runtime Libraries

The core eXtremeDB runtime functionality is encapsulated in the extremedb.jar archive which is compiled together with the Java application. Then the following Database configuration values can be set to dynamically load the associated library when a Database is instantiated, however, note that no additional library is necessary for SQL support:

MCO_CFG_DEBUG_LIBRARY

Load debug versions of libraries to provide additional diagnostic exceptions

MCO_CFG_DISK_SUPPORT

Load "_disk" versions of libraries for databases on persistent storage devices

MCO_CFG_SHARED_MEMORY

Load "_shm" versions of libraries for databases using shared memory

MCO_CFG_MVCC_TRANSACTION_MANAGER

Load "_mvcc" versions of libraries to use the MVCC transaction manager - by default "_mursiw" (MURSIW transaction manager) versions are loaded

MCO_CFG_DEBUG_LIBRARY	Load debug versions of libraries to provide additional diagnostic exceptions
MCO_CFG_DISK_SUPPORT	Load "`_disk`" versions of libraries for databases on persistent storage devices
MCO_CFG_SHARED_MEMORY	Load "`_shm`" versions of libraries for databases using shared memory
MCO_CFG_MVCC_TRANSACTION_MANAGER	Load "`_mvcc`" versions of libraries to use the MVCC transaction manager - by default "`_mursiw`" (MURSIW transaction manager) versions are loaded