From 6b74b7c2559563a4c78a8b917cd0044f795d5d2b Mon Sep 17 00:00:00 2001 From: sjaanus Date: Tue, 6 Dec 2022 13:57:54 +0100 Subject: [PATCH] Fix error in migration when updating feature_environments (#2607) Fixes a issue, where `variants` was null in features table, but column is not nullable. Co-authored-by: sighphyre --- .../20221107121635-move-variants-to-per-environment.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/migrations/20221107121635-move-variants-to-per-environment.js b/src/migrations/20221107121635-move-variants-to-per-environment.js index 3ce7abc116..6dad2afc4f 100644 --- a/src/migrations/20221107121635-move-variants-to-per-environment.js +++ b/src/migrations/20221107121635-move-variants-to-per-environment.js @@ -5,7 +5,8 @@ exports.up = function (db, callback) { ` ALTER TABLE feature_environments ADD COLUMN variants JSONB DEFAULT '[]'::jsonb NOT NULL; WITH feature_variants AS (SELECT variants, name FROM features) - UPDATE feature_environments SET variants = feature_variants.variants FROM feature_variants WHERE feature_name = feature_variants.name; + UPDATE feature_environments SET variants = feature_variants.variants FROM feature_variants + WHERE feature_name = feature_variants.name and feature_variants.variants is not null; CREATE VIEW features_view AS SELECT