Mercurial > gemma
comparison pkg/imports/fd.go @ 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 | a7c4005b723f |
children | 2b72f5e005aa |
comparison
equal
deleted
inserted
replaced
1994:a7c4005b723f | 1995:59055c8301df |
---|---|
119 | 119 |
120 const ( | 120 const ( |
121 fdStageDoneSQL = ` | 121 fdStageDoneSQL = ` |
122 UPDATE waterway.fairway_dimensions SET staging_done = true | 122 UPDATE waterway.fairway_dimensions SET staging_done = true |
123 WHERE id IN ( | 123 WHERE id IN ( |
124 SELECT key from waterway.track_imports | 124 SELECT key from import.track_imports |
125 WHERE import_id = $1 AND | 125 WHERE import_id = $1 AND |
126 relation = 'waterway.fairway_dimensions'::regclass)` | 126 relation = 'waterway.fairway_dimensions'::regclass)` |
127 | 127 |
128 deleteFairwayDimensionSQL = ` | 128 deleteFairwayDimensionSQL = ` |
129 WITH resp AS ( | 129 WITH resp AS ( |