Mercurial > gemma

diff schema/gemma.sql @ 4111:692aba3e8b85 request_hist_bns

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Change constraints for bottlenecks to include staging_done flag. This will allow us to stage not only new bottlenecks but also updates.
author Sascha Wilde <wilde@intevation.de>
date Tue, 30 Jul 2019 13:14:47 +0200
parents 7711486efaba
children 8c62809ea87e
line wrap: on
line diff
--- a/schema/gemma.sql	Tue Jul 30 11:30:31 2019 +0200
+++ b/schema/gemma.sql	Tue Jul 30 13:14:47 2019 +0200
@@ -649,9 +649,6 @@
         id int PRIMARY KEY GENERATED BY DEFAULT AS IDENTITY,
         bottleneck_id varchar NOT NULL,
         validity tstzrange NOT NULL CHECK (NOT isempty(validity)),
-        UNIQUE (bottleneck_id, validity),
-        EXCLUDE USING GiST (bottleneck_id WITH =, validity WITH &&)
-            DEFERRABLE INITIALLY DEFERRED,
         gauge_location isrs NOT NULL,
         objnam varchar,
         nobjnm varchar,
@@ -673,7 +670,12 @@
         -- XXX: Also an attribut of sounding result?
         date_info timestamp with time zone NOT NULL,
         source_organization varchar NOT NULL,
-        staging_done boolean NOT NULL DEFAULT false
+        staging_done boolean NOT NULL DEFAULT false,
+        UNIQUE (bottleneck_id, validity, staging_done),
+        EXCLUDE USING GiST (bottleneck_id WITH =,
+                            validity WITH &&,
+                            CAST(staging_done AS int) WITH =)
+            DEFERRABLE INITIALLY DEFERRED
     )
     CREATE CONSTRAINT TRIGGER waterway_bottlenecks_reference_gauge
         AFTER INSERT OR UPDATE OF gauge_location ON bottlenecks