Mercurial > gemma
comparison schema/tap_tests_data.sql @ 567:f3452ce5c056
Make table writable for data import
Lookup tables will probably be filled with data during import and
thus should reside in the waterway schema, which is accordingly
authorised. Touch only the one table relevant for bottlenecks here, as
other data might be handled differently. Lookup tables referenced
in out-commented columns not touched, as it is not yet clarified
whether these columns will be removed completely. countries not touched
neither, because it will be filled from different source and demo-data
should have everything necessary to start importing bottlenecks.
| author | Tom Gottfried <tom@intevation.de> |
|---|---|
| date | Tue, 04 Sep 2018 21:41:45 +0200 |
| parents | 3af7ca761f6a |
| children | e6c9d2da2e20 |
comparison
equal
deleted
inserted
replaced
| 566:5e45f441aed6 | 567:f3452ce5c056 |
|---|---|
| 15 INSERT INTO users.list_users VALUES ( | 15 INSERT INTO users.list_users VALUES ( |
| 16 'waterway_admin', 'test_admin_at', 'admin_at1$', 'AT', NULL, 'yyy'); | 16 'waterway_admin', 'test_admin_at', 'admin_at1$', 'AT', NULL, 'yyy'); |
| 17 INSERT INTO users.list_users VALUES ( | 17 INSERT INTO users.list_users VALUES ( |
| 18 'sys_admin', 'test_sys_admin1', 'sys_admin1$', 'AT', NULL, 'zzz'); | 18 'sys_admin', 'test_sys_admin1', 'sys_admin1$', 'AT', NULL, 'zzz'); |
| 19 | 19 |
| 20 INSERT INTO limiting_factors VALUES ('depth'), ('width'); | 20 INSERT INTO waterway.limiting_factors VALUES ('depth'), ('width'); |
| 21 | 21 |
| 22 INSERT INTO waterway.gauges ( | 22 INSERT INTO waterway.gauges ( |
| 23 location, function_code, objname, geom, zero_point, source_organization) | 23 location, function_code, objname, geom, zero_point, source_organization) |
| 24 VALUES ( | 24 VALUES ( |
| 25 ('AT', 'XXX', '00001', '00000', 1)::isrs, | 25 ('AT', 'XXX', '00001', '00000', 1)::isrs, |