Mercurial > gemma
changeset 62:39e0e3d8dd1b
Comment potentially obsolete table out.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Fri, 25 May 2018 21:20:32 +0200 |
parents | a5749fd004c3 |
children | c18f1db22077 |
files | wamos.sql |
diffstat | 1 files changed, 12 insertions(+), 12 deletions(-) [+] |
line wrap: on
line diff
--- a/wamos.sql Fri May 25 19:25:05 2018 +0200 +++ b/wamos.sql Fri May 25 21:20:32 2018 +0200 @@ -29,18 +29,18 @@ -- Eventually obsolete. -- See https://roundup-intern.intevation.de/wamos/issue5 -CREATE TABLE rwdrs ( - stretch isrsrange PRIMARY KEY, - -- https://www.postgresql.org/docs/10/static/sql-createindex.html: - -- Only B-tree supports UNIQUE indexes, but we need the GIST index - -- below anyhow. - -- Is it a good idea to build B-tree indexes on relatively large - -- composites of string values or should we use inter PKs? - -- => In case the index is used and cache space becomes a limiting - -- factor, this might be an issue. - rwdr double precision NOT NULL, - EXCLUDE USING GIST (stretch WITH &&) - ); +-- CREATE TABLE rwdrs ( +-- stretch isrsrange PRIMARY KEY, +-- -- https://www.postgresql.org/docs/10/static/sql-createindex.html: +-- -- Only B-tree supports UNIQUE indexes, but we need the GIST index +-- -- below anyhow. +-- -- Is it a good idea to build B-tree indexes on relatively large +-- -- composites of string values or should we use inter PKs? +-- -- => In case the index is used and cache space becomes a limiting +-- -- factor, this might be an issue. +-- rwdr double precision NOT NULL, +-- EXCLUDE USING GIST (stretch WITH &&) +-- ); CREATE TABLE gauges ( location isrs PRIMARY KEY,