Mercurial > gemma

comparison schema/gemma.sql @ 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 337e9f85f84c
children 02951a62e8c6
comparison
equal deleted inserted replaced
3622:30a9fdac70f0 3624:3012d0b3badc
535 UNIQUE (bottleneck_id, date_info), 535 UNIQUE (bottleneck_id, date_info),
536 area geography(POLYGON, 4326) NOT NULL 536 area geography(POLYGON, 4326) NOT NULL
537 CHECK(ST_IsValid(CAST(area AS geometry))), 537 CHECK(ST_IsValid(CAST(area AS geometry))),
538 surtyp varchar REFERENCES survey_types, 538 surtyp varchar REFERENCES survey_types,
539 coverage varchar REFERENCES coverage_types, 539 coverage varchar REFERENCES coverage_types,
540 depth_reference varchar(4) NOT NULL, -- REFERENCES depth_references, 540 depth_reference varchar NOT NULL, -- REFERENCES depth_references,
541 octree_checksum varchar, 541 octree_checksum varchar,
542 octree_index bytea, 542 octree_index bytea,
543 staging_done boolean NOT NULL DEFAULT false 543 staging_done boolean NOT NULL DEFAULT false
544 ) 544 )
545 545