Key	Description
`durable`	Durable database transactions assuming a media of that type. This is the highest level of transaction safeness. The user should never loose any data assuming the underlying media is durable.
`consistent`	Consistent database transactions assuming a media of that type. This is a medium level of transaction safeness. The user may lose data in the case the operating system crashes or shuts down without flushing its file system buffers. Recovery will ensure a consistent state where a partial transaction should never be observed.
`unsafe`	Unsafe database transactions. This is the lowest level of transaction safeness. The user may lose data including the entire database in the case the operating system crashes or shuts down without flushing its file system cache. All users of a given database should request this mode for this to take affect. Use of this option may affect later sessions that are specified as durable or constent. Use an OS command or other means to flush file system buffers to permanent storage to be safe. The command line tool 'sync' can be used on Unix

Note: Durability will be elevated to CONSISTENT unless all database connections have specified UNSAFE.

Default Value: If the durability option is not defined, the default value of DURABLE is used.

Example: durability= DURABLE

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:

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: