Mercurial > gemma
comparison wamos.sql @ 62:39e0e3d8dd1b
Comment potentially obsolete table out.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Fri, 25 May 2018 21:20:32 +0200 |
parents | f0ca64da9446 |
children | 1e9589cf9c00 |
comparison
equal
deleted
inserted
replaced
61:a5749fd004c3 | 62:39e0e3d8dd1b |
---|---|
27 subtype = isrs | 27 subtype = isrs |
28 ); | 28 ); |
29 | 29 |
30 -- Eventually obsolete. | 30 -- Eventually obsolete. |
31 -- See https://roundup-intern.intevation.de/wamos/issue5 | 31 -- See https://roundup-intern.intevation.de/wamos/issue5 |
32 CREATE TABLE rwdrs ( | 32 -- CREATE TABLE rwdrs ( |
33 stretch isrsrange PRIMARY KEY, | 33 -- stretch isrsrange PRIMARY KEY, |
34 -- https://www.postgresql.org/docs/10/static/sql-createindex.html: | 34 -- -- https://www.postgresql.org/docs/10/static/sql-createindex.html: |
35 -- Only B-tree supports UNIQUE indexes, but we need the GIST index | 35 -- -- Only B-tree supports UNIQUE indexes, but we need the GIST index |
36 -- below anyhow. | 36 -- -- below anyhow. |
37 -- Is it a good idea to build B-tree indexes on relatively large | 37 -- -- Is it a good idea to build B-tree indexes on relatively large |
38 -- composites of string values or should we use inter PKs? | 38 -- -- composites of string values or should we use inter PKs? |
39 -- => In case the index is used and cache space becomes a limiting | 39 -- -- => In case the index is used and cache space becomes a limiting |
40 -- factor, this might be an issue. | 40 -- -- factor, this might be an issue. |
41 rwdr double precision NOT NULL, | 41 -- rwdr double precision NOT NULL, |
42 EXCLUDE USING GIST (stretch WITH &&) | 42 -- EXCLUDE USING GIST (stretch WITH &&) |
43 ); | 43 -- ); |
44 | 44 |
45 CREATE TABLE gauges ( | 45 CREATE TABLE gauges ( |
46 location isrs PRIMARY KEY, | 46 location isrs PRIMARY KEY, |
47 dummy_attrib varchar, | 47 dummy_attrib varchar, |
48 "..." varchar | 48 "..." varchar |