The following lists some of the tables that the Registry creates, along with a description of the tables' purpose.
Important Notes: The database tables are primarily used for persistence of Registry information. Do not expect modifying database values to have any effect on a running Registry. Regnology does not recommend modifying database tables unless explicitly instructed to do so.
Structural Metadata Persistence
| Table Name
|
Description
|
| registry_maintainables
|
A list of all the maintainables in the Registry.
|
| registry_maintainable_sdmx
|
Each maintainable in the Registry stored in its SDMX form.
|
| registry_maintainable_ser
|
Each maintainable in the Registry stored as a Java serialised object. This is used for performance purposes as de-serialising a serialised object is faster than recreating it from its SDMX form.
|
Transactional Information
| Table Name
|
Description
|
| tx_backup
|
Stores the transaction number for each individual structure submission / modification. Note a single transaction can be for multiple metadata structures
|
| sdmx_transaction
|
Stores information about each transaction, such as the user who performed it, the date and event type (Replace, Delete, etc)
|
| sdmx_transaction_item
|
Links the URN of a individual structural metadata to a transaction number.
|
| sdmx_backup
|
Stores a binary image of the transaction in gzipped format of the XML
|
Registry Settings
| Table Name
|
Description
|
| registry_settings
|
Persists most of the registry settings in a key / value format where the column "name" identifies the setting and the column "value" its value.
|
| registry_settings_dv
|
Persists the data validation settings of the Registry
|
| registry_settings_ser
|
Serialised Registry settings. This is used for when the the setting to be stored cannot be described as a string in the registry_settings table and its serialised form needs to be persisted.
|
