Mercurial > gemma
changeset 3535:337e9f85f84c
Prevent non-erased gauge version to have empty validity range
This is a follow-up to revision ba0339118d9c, that did not introduce
such constraint by virtue of missing that we have the information
which gauge is 'current' readily at hand in the erased flag.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Wed, 29 May 2019 18:41:35 +0200 |
parents | 8e083b271fca |
children | 1422ca0e6a51 cbf883596e4e |
files | schema/gemma.sql |
diffstat | 1 files changed, 1 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/schema/gemma.sql Wed May 29 18:14:20 2019 +0200 +++ b/schema/gemma.sql Wed May 29 18:41:35 2019 +0200 @@ -288,6 +288,7 @@ lastupdate timestamp with time zone NOT NULL, -- entry removed from external data source (RIS-Index)/historicised: erased boolean NOT NULL DEFAULT false, + CHECK (erased OR NOT isempty(validity)), PRIMARY KEY (location, validity), EXCLUDE USING GiST (isrs_astext(location) WITH =, validity WITH &&) DEFERRABLE INITIALLY DEFERRED