stackrox · c-du · Nov 16, 2022 · Nov 10, 2022 · Nov 10, 2022 · Nov 10, 2022
diff --git a/central/vulnerabilityrequest/datastore/internal/store/postgres/gen.go b/central/vulnerabilityrequest/datastore/internal/store/postgres/gen.go
@@ -1,3 +1,3 @@
 package postgres
 
-//go:generate pg-table-bindings-wrapper --type=storage.VulnerabilityRequest --search-category VULN_REQUEST --permission-checker permissionCheckerSingleton() --migration-seq 53 --migrate-from rocksdb
+//go:generate pg-table-bindings-wrapper --type=storage.VulnerabilityRequest --search-category VULN_REQUEST --permission-checker permissionCheckerSingleton()
diff --git a/central/vulnerabilityrequest/datastore/internal/store/rocksdb/gen.go b/central/vulnerabilityrequest/datastore/internal/store/rocksdb/gen.go
@@ -1,3 +1,3 @@
 package rocksdb
 
-//go:generate rocksdb-bindings-wrapper --type=VulnerabilityRequest --bucket=vuln_req --migration-seq 53 --migrate-to vulnerability_requests
+//go:generate rocksdb-bindings-wrapper --type=VulnerabilityRequest --bucket=vuln_req
@@ -0,0 +1,9 @@
+# Frozen Schemas
+The schemas in Central are evolving. Migrations are created to upgrade Central
+databases from one version to another. Data migrations are based on the schemas at
+that particular release and should not evolve with Central.
+
+We create a copy of schemas and freeze it here so that the migrations can use them to upgrade
+legacy databases. All schemas are frozen for version
+3.73 to support upgrade from RocksDB and BoltDb to Postgres. Note this is not mandatory for every release. In a more common scenario,
+if we need to create one migration for one table, you can keep the frozen schema in the migration itself.