storage

This option sets the storage type of the databases opened under this TFS handle. Supported values are:

Value	Description
ondisk	Use the disk-based engine
inmemory_volatile	Use the in-memory engine. The database is empty when the first client opens it and all contents are discarded when the last client closes it.
inmemory_load	Use the in-memory engine. The database contents are loaded from disk when the first client opens it and contents are not automatically saved when the last client closes it.
inmemory_keep	Use the in-memory engine. The database is empty when the first client opens it and any rows in the database will be written to disk when the last client closes it. Any existing disk-based files will be overwritten by the contents of the in-memory database.
inmemory_persist	Use the in-memory engine. The database contents are loaded from disk when the first client opens it and contents are automatically saved when the last client closes it.

Default Value

If the storage option is not defined, the default value of ONDISK is used.

Example

storage=ONDISK

Database Configuration Options

This option key is associated with the RDM_DB handle (or RDM_CPP::Db for C++) and can be set using one of the following functions:

• SQLSetConnectAttr()
• rdm_dbSetOption()
• rdm_dbSetOptions()
• RDM_CPP::Db::SetOption()
• RDM_CPP::Db::SetOptions()

The option key can also be associated with the RDM_TFS handle (or RDM_CPP::TFS for C++) which will be inherited by the next RDM_DB handle (or RDM_CPP::Db for C++) allocated. Modifications to the RDM_TFS after the RDM_DB is allocated have no effect on the allocated RDM_DB. The following functions can be used to set the key/values to be inherited later:

• rdm_tfsSetOptions()
• rdm_tfsSetOption()
• RDM_CPP::TFS::SetOption()
• RDM_CPP::TFS::SetOptions()