comparison schema/gemma.sql @ 1780:48791416bea5

(Approved) gauge measurement import: Fixed row level security.
author Sascha L. Teichmann <sascha.teichmann@intevation.de>
date Fri, 11 Jan 2019 16:48:14 +0100
parents fcb0106ec510
children 8fd132b9cdbd
comparison
equal deleted inserted replaced
1779:ad1c12e999df 1780:48791416bea5
282 -- XXX: Do we need "unit" attribute or can we normalise on import? 282 -- XXX: Do we need "unit" attribute or can we normalise on import?
283 value_min double precision, -- XXX: NOT NULL if predicted? 283 value_min double precision, -- XXX: NOT NULL if predicted?
284 value_max double precision, -- XXX: NOT NULL if predicted? 284 value_max double precision, -- XXX: NOT NULL if predicted?
285 --- TODO: Add a double range type for checking? 285 --- TODO: Add a double range type for checking?
286 date_info timestamp with time zone NOT NULL DEFAULT CURRENT_TIMESTAMP, 286 date_info timestamp with time zone NOT NULL DEFAULT CURRENT_TIMESTAMP,
287 source_organization varchar NOT NULL -- "originator" 287 source_organization varchar NOT NULL, -- "originator"
288 -- XXX removed staging done temporarily. Currently imported raw data is 288 staging_done boolean NOT NULL DEFAULT false
289 -- not staged. When importing approved gauge measurements uncomment this
290 -- and add policy to allow select on this table for waterway_admin
291 -- staging_done boolean NOT NULL DEFAULT false
292 ) 289 )
293 CREATE TRIGGER gauge_measurements_date_info 290 CREATE TRIGGER gauge_measurements_date_info
294 BEFORE UPDATE ON gauge_measurements 291 BEFORE UPDATE ON gauge_measurements
295 FOR EACH ROW EXECUTE PROCEDURE update_date_info() 292 FOR EACH ROW EXECUTE PROCEDURE update_date_info()
296 293