It is only required to set the database handle collate option when first creating a database. Once the database has been created with locale collation the database can be opened without explicitly setting the collate option in the database handle.

Warning: If the collate option is set and the database already exists, the collate option must be an exact match with the collate string stored in the database catalog.; Using a locale specific location can result in a database that is not compatible with cross-platform data access unless the collate string matches exactly.; A database collate value cannot be changed.

RDM utilizes local locale functionality on operating systems where it is supported. On those operating systems, the locale of the application does not need to match the locale used by the database. On operating systems where local locales are not supported, the collation locale of the thread(s) using the database must match the locale stored in the database catalog. If the locales do not match the eLOCALEMISMATCH error code will be returned when the when a database is requested.

Default Value

The default value for collate is NULL if the database is being created.

Example

collate=en_DK.utf8

Note: Only .utf8 locales are supported for the collate option.

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: