Move schema changes to 1.11.9

Author: harshach

bootstrap/sql/migrations/native/1.11.8/mysql/schemaChanges.sql

@@ -23,14 +23,4 @@ WHERE
 -- Upgrade appliedAt to microsecond precision to match PostgreSQL behavior.
 -- Without this, MySQL returns second-precision timestamps which cause spurious
 -- diffs in JSON patch operations, leading to deserialization failures.
-ALTER TABLE tag_usage MODIFY appliedAt TIMESTAMP(6) NULL DEFAULT CURRENT_TIMESTAMP(6);
-
--- Change entity_extension_time_series.timestamp from VIRTUAL to STORED for performance.
--- STORED columns are materialized on disk, making unique constraint checks and range
--- queries on timestamp significantly faster (especially for bulk pipeline status upserts).
--- MySQL does not allow ALTER from VIRTUAL to STORED directly, so we drop and re-add.
-ALTER TABLE entity_extension_time_series
-  DROP INDEX entity_extension_time_series_constraint,
-  DROP COLUMN `timestamp`,
-  ADD COLUMN `timestamp` bigint unsigned GENERATED ALWAYS AS (json_unquote(json_extract(`json`, _utf8mb4'$.timestamp'))) STORED NOT NULL,
-  ADD UNIQUE KEY `entity_extension_time_series_constraint` (`entityFQNHash`, `extension`, `timestamp`);
+ALTER TABLE tag_usage MODIFY appliedAt TIMESTAMP(6) NULL DEFAULT CURRENT_TIMESTAMP(6);

bootstrap/sql/migrations/native/1.11.8/postgres/schemaChanges.sql

@@ -11,7 +11,3 @@ WHERE serviceType = 'Salesforce'
   AND json->'connection'->'config'->>'sobjectName' IS NOT NULL;
 
 -- No changes needed for PostgreSQL - TIMESTAMP already has microsecond precision.
-
--- No changes needed for entity_extension_time_series.timestamp on PostgreSQL.
--- PostgreSQL already uses STORED for the generated timestamp column (since table creation).
--- MySQL migration changes it from VIRTUAL to STORED for consistency and performance.

bootstrap/sql/migrations/native/1.11.9/mysql/schemaChanges.sql

@@ -0,0 +1,11 @@
+-- Change entity_extension_time_series.timestamp from VIRTUAL to STORED for performance.
+-- STORED columns are materialized on disk, making unique constraint checks and range
+-- queries on timestamp significantly faster (especially for bulk pipeline status upserts).
+-- MySQL does not allow ALTER from VIRTUAL to STORED directly, so we drop and re-add.
+-- NOTE: This will lock the table for a full rebuild. On large deployments with millions
+-- of rows in entity_extension_time_series, plan for downtime accordingly.
+ALTER TABLE entity_extension_time_series
+  DROP INDEX entity_extension_time_series_constraint,
+  DROP COLUMN `timestamp`,
+  ADD COLUMN `timestamp` bigint unsigned GENERATED ALWAYS AS (json_unquote(json_extract(`json`, _utf8mb4'$.timestamp'))) STORED NOT NULL,
+  ADD UNIQUE KEY `entity_extension_time_series_constraint` (`entityFQNHash`, `extension`, `timestamp`);

bootstrap/sql/migrations/native/1.11.9/postgres/schemaChanges.sql

@@ -0,0 +1,3 @@
+-- No changes needed for entity_extension_time_series.timestamp on PostgreSQL.
+-- PostgreSQL already uses STORED for the generated timestamp column (since table creation).
+-- MySQL migration changes it from VIRTUAL to STORED for consistency and performance.