Mercurial > gemma

diff schema/gemma.sql @ 3529:ba0339118d9c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Improve validation of gauge temporal validity The current version of a gauge should always have a validity represented by a non-empty time range. Thus, do not accept empty time ranges on input. Nevertheless, continue to accept storing empty time ranges (no CHECK constraint), because a new version with equal start date but longer validity might still cause the previous version to get an empty time range. In passing, add a missing NOT NULL constraint: if both start and end date are omitted, the range will be unbounded, but it should never be NULL.
author Tom Gottfried <tom@intevation.de>
date Wed, 29 May 2019 16:43:26 +0200
parents 6592396f5061
children 8e083b271fca
line wrap: on
line diff
--- a/schema/gemma.sql	Wed May 29 16:00:28 2019 +0200
+++ b/schema/gemma.sql	Wed May 29 16:43:26 2019 +0200
@@ -280,7 +280,7 @@
         geom geography(POINT, 4326) NOT NULL,
         applicability_from_km int8,
         applicability_to_km int8,
-        validity tstzrange,
+        validity tstzrange NOT NULL,
         zero_point double precision NOT NULL,
         geodref varchar,
         date_info timestamp with time zone NOT NULL,