Explanation of Registry Tables - Revision history

Vmurrell at 10:58, 30 March 2024

2024-03-30T10:58:03Z

Vmurrell at 08:52, 14 August 2023

2023-08-14T08:52:02Z

Vmurrell at 09:33, 20 July 2023

2023-07-20T09:33:12Z

Plazarou: /* Auditing and Logging */

2023-02-13T13:39:19Z

‎Auditing and Logging

Plazarou: /* Auditing and Logging */

2023-02-13T13:35:35Z

‎Auditing and Logging

Plazarou: /* Auditing and Logging */

2023-02-13T13:30:27Z

‎Auditing and Logging

Plazarou: /* Auditing and Logging */

2023-02-13T13:24:19Z

‎Auditing and Logging

Plazarou at 13:22, 13 February 2023

2023-02-13T13:22:05Z

Plazarou: Created page with " The following lists some of the tables that the Registry creates with a description of the tables purpose. '''Note:''' the database tables are primarily used for persistence..."

2022-04-12T13:40:17Z

Created page with " The following lists some of the tables that the Registry creates with a description of the tables purpose. '''Note:''' the database tables are primarily used for persistence..."

New page

The following lists some of the tables that the Registry creates with a description of the tables purpose.

'''Note:''' 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. Metadata Technology does not recommend modifying database tables unless explicitly instructed to do so.

==== Structural Metadata Persistence ====
{| class="wikitable"
!|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 ====
{| class="wikitable"
!|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 ====
{| class="wikitable"
!|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.
|}

← Older revision		Revision as of 10:58, 30 March 2024
Line 1:		Line 1:
		+	__NOTOC__
	[[Category:Concepts_Reference_V11]]		[[Category:Concepts_Reference_V11]]
	The following lists some of the tables that the Registry creates with a description of the tables purpose.		The following lists some of the tables that the Registry creates with a description of the tables purpose.

← Older revision		Revision as of 09:33, 20 July 2023
Line 1:		Line 1:
−		+	[[Category:Concepts_Reference_V11]]
	The following lists some of the tables that the Registry creates with a description of the tables purpose.		The following lists some of the tables that the Registry creates with a description of the tables purpose.

@@ Line 61: / Line 61: @@
 |-
 |registry_logs
-|For every recorded log event in the Registry, the time taken and Transaction Id (if appropriate) are recorded
+|For every recorded log event in the Registry, a row is stored with the time taken and Transaction Id (if appropriate)
 |-
 |registry_logs_zip
 |The zipped up store of the logging information for a particular log event. This information is usually sent to the Apache Tomcat "Registry.log" file, but for any particular request, the same information is stored in a zipped form.
 |}

@@ Line 61: / Line 61: @@
 |-
 |registry_logs
-|TODO2
+|For every recorded log event in the Registry, the time taken and Transaction Id (if appropriate) are recorded
 |-
 |registry_logs_zip
-|The zipped up store of the logging information for a particular request. This information is usually sent to the Apache Tomcat "Registry.log" file, but for any particular request, the same information is stored in a zipped form.
+|The zipped up store of the logging information for a particular log event. This information is usually sent to the Apache Tomcat "Registry.log" file, but for any particular request, the same information is stored in a zipped form.
 |}

@@ Line 64: / Line 64: @@
 |-
 |registry_logs_zip
-|TODO3
+|The zipped up store of the logging information for a particular request. This information is usually sent to the Apache Tomcat "Registry.log" file, but for any particular request, the same information is stored in a zipped form.
 |}

@@ Line 2: / Line 2: @@
 The following lists some of the tables that the Registry creates with a description of the tables purpose.
-'''Note:''' 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. Metadata Technology does not recommend modifying database tables unless explicitly instructed to do so.
+'''Note:''' 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. It is recommended to NOT modify database tables unless explicitly instructed to do so.
 ==== Structural Metadata Persistence ====

@@ Line 58: / Line 58: @@
 |-
 |registry_audit
-|TODO1
+|Stores Audit information from HTTP requests, such as the requested Web Service, information about the requesting machine and the associated transaction_id (if appropriate)
 |-
 |registry_logs

@@ Line 50: / Line 50: @@
 |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.
 |}