Mercurial > gemma

comparison schema/gemma.sql @ 4070:4332b9e26e2f historization_ng

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Merged default
author Sascha Wilde <wilde@intevation.de>
date Thu, 25 Jul 2019 13:20:32 +0200
parents 76482935b6e5 b79b60c0cc5a
children c1c6a375305f
comparison
equal deleted inserted replaced
4069:12f476e91c70 4070:4332b9e26e2f
727 bottleneck_id varchar NOT NULL, 727 bottleneck_id varchar NOT NULL,
728 surdat date NOT NULL, 728 surdat date NOT NULL,
729 UNIQUE (bottleneck_id, surdat), 729 UNIQUE (bottleneck_id, surdat),
730 -- additional_data xml -- Currently not relevant for GEMMA 730 -- additional_data xml -- Currently not relevant for GEMMA
731 critical boolean, 731 critical boolean,
732 date_info timestamp with time zone NOT NULL DEFAULT CURRENT_TIMESTAMP, 732 date_info timestamp with time zone NOT NULL,
733 source_organization varchar NOT NULL 733 source_organization varchar NOT NULL
734 ) 734 )
735 CREATE TRIGGER fairway_availability_date_info
736 BEFORE UPDATE ON fairway_availability
737 FOR EACH ROW EXECUTE PROCEDURE update_date_info()
738 -- FIXME: From the DRC it is unclear what the exact semantics of 735 -- FIXME: From the DRC it is unclear what the exact semantics of
739 -- surdat and Date_Info ar unclear. Currently we assume that 736 -- surdat and Date_Info ar unclear. Currently we assume that
740 -- (fk_bn_fid,surdat) has to be unique, but that might be false. 737 -- (fk_bn_fid,surdat) has to be unique, but that might be false.
741 -- Anyway, I will date_info here to check for an matching 738 -- Anyway, I will date_info here to check for an matching
742 -- reference gauge at the bottleneck. The reason for this 739 -- reference gauge at the bottleneck. The reason for this