Mercurial > gemma
diff schema/tap_tests_data.sql @ 1995:59055c8301df
Move import queue to its own database namespace
Authorisation of the import queue has to be handled differently
from the waterway-related data in the waterway schema. This is
easier to handle, if both are in their own schema/namespace.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Thu, 24 Jan 2019 12:56:31 +0100 |
parents | f9f1babe52ae |
children | b66cfcde8ff7 |
line wrap: on
line diff
--- a/schema/tap_tests_data.sql Thu Jan 24 12:50:17 2019 +0100 +++ b/schema/tap_tests_data.sql Thu Jan 24 12:56:31 2019 +0100 @@ -95,17 +95,17 @@ WITH job AS ( - INSERT INTO waterway.imports (kind, username, data) VALUES ( + INSERT INTO import.imports (kind, username, data) VALUES ( 'test', 'test_admin_ro', 'test') RETURNING id), log AS ( - INSERT INTO waterway.import_logs (import_id, msg) + INSERT INTO import.import_logs (import_id, msg) SELECT id, 'test' FROM job) -INSERT INTO waterway.track_imports +INSERT INTO import.track_imports SELECT id, 'waterway.bottlenecks', 1 FROM job; WITH config AS ( - INSERT INTO waterway.import_configuration (kind, username) VALUES ( + INSERT INTO import.import_configuration (kind, username) VALUES ( 'test', 'test_admin_ro') RETURNING id) -INSERT INTO waterway.import_configuration_attributes +INSERT INTO import.import_configuration_attributes SELECT id, 'test key', 'test value' FROM config;