Add catalog_verified_namespace table
What does this MR do and why?
Creates catalog_verified_namespaces
table in favour of #439390 (closed)
Add specs to the model
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Migrations
UP
main: == [advisory_lock_connection] object_id: 117800, pg_backend_pid: 74892
main: == 20240128140259 CreateCatalogVerifiedNamespaces: migrating ==================
main: -- create_table(:catalog_verified_namespaces)
main: -> 0.0049s
main: == 20240128140259 CreateCatalogVerifiedNamespaces: migrated (0.0147s) =========
main: == [advisory_lock_connection] object_id: 117800, pg_backend_pid: 74892
ci: == [advisory_lock_connection] object_id: 118080, pg_backend_pid: 74894
ci: == 20240128140259 CreateCatalogVerifiedNamespaces: migrating ==================
ci: -- create_table(:catalog_verified_namespaces)
ci: -> 0.0094s
I, [2024-01-28T22:20:02.634070 #74745] INFO -- : Database: 'ci', Table: 'catalog_verified_namespaces': Lock Writes
ci: == 20240128140259 CreateCatalogVerifiedNamespaces: migrated (0.0194s) =========
ci: == [advisory_lock_connection] object_id: 118080, pg_backend_pid: 74894
Down
main: == [advisory_lock_connection] object_id: 117300, pg_backend_pid: 75394
main: == 20240128140259 CreateCatalogVerifiedNamespaces: reverting ==================
main: -- drop_table(:catalog_verified_namespaces)
main: -> 0.0020s
main: == 20240128140259 CreateCatalogVerifiedNamespaces: reverted (0.0084s) =========
main: == [advisory_lock_connection] object_id: 117300, pg_backend_pid: 75394
How to set up and validate locally
- Migration should run without any issue.
- Since this table is not yet used elsewhere, it won't have any visual changes.
Related to #439390 (closed)