Mercurial > gemma

changeset 3624:3012d0b3badc

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Allow same values for depth_reference in SR as in gauges The depth_reference in a sounding result references a depth_reference of the bottlenecks reference gauge. Therefor the same values must be accepted, which means the restriction to four chars is no good. In the real world this might be something as "LDC2010", which is obviously longer.
author Sascha Wilde <wilde@intevation.de>
date Wed, 05 Jun 2019 18:50:54 +0200
parents 30a9fdac70f0
children a688a478e35f 943c454d5633 6d6577a87963
files schema/gemma.sql
diffstat 1 files changed, 1 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/schema/gemma.sql	Wed Jun 05 16:38:26 2019 +0200
+++ b/schema/gemma.sql	Wed Jun 05 18:50:54 2019 +0200
@@ -537,7 +537,7 @@
             CHECK(ST_IsValid(CAST(area AS geometry))),
         surtyp varchar REFERENCES survey_types,
         coverage varchar REFERENCES coverage_types,
-        depth_reference varchar(4) NOT NULL, -- REFERENCES depth_references,
+        depth_reference varchar NOT NULL, -- REFERENCES depth_references,
         octree_checksum varchar,
         octree_index bytea,
         staging_done boolean NOT NULL DEFAULT false