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 <liquidwicked64@gmail.com>
Unleash · Dec 6, 2022 · 6b74b7c · 6b74b7c
1 parent fdd0509
commit 6b74b7c
Showing 1 changed file with 2 additions and 1 deletion.
diff --git 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