feat: constrain table to ensure at most one config can be active per kit

AstroPlant · Mar 21, 2024 · 3592341 · 3592341
1 parent 95bd131
commit 3592341
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/migrations/2024-03-21-205107_make-active-kit-configuration-partially-unique/down.sql b/migrations/2024-03-21-205107_make-active-kit-configuration-partially-unique/down.sql
@@ -0,0 +1 @@
+DROP INDEX ix_kit_configurations_active_kit_id
diff --git a/migrations/2024-03-21-205107_make-active-kit-configuration-partially-unique/up.sql b/migrations/2024-03-21-205107_make-active-kit-configuration-partially-unique/up.sql
@@ -0,0 +1,4 @@
+CREATE UNIQUE INDEX ix_kit_configurations_active_kit_id ON public.kit_configurations (kit_id)
+WHERE (active);
+
+COMMENT ON INDEX ix_kit_configurations_active_kit_id IS 'At most one kit configuration may be active per kit at any one time.'