Mercurial > gemma
comparison pkg/imports/bn.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 | d966f03ea819 |
| children | b868cb653c4d |
comparison
equal
deleted
inserted
replaced
| 1994:a7c4005b723f | 1995:59055c8301df |
|---|---|
| 105 | 105 |
| 106 const ( | 106 const ( |
| 107 bnStageDoneSQL = ` | 107 bnStageDoneSQL = ` |
| 108 UPDATE waterway.bottlenecks SET staging_done = true | 108 UPDATE waterway.bottlenecks SET staging_done = true |
| 109 WHERE id IN ( | 109 WHERE id IN ( |
| 110 SELECT key from waterway.track_imports | 110 SELECT key from import.track_imports |
| 111 WHERE import_id = $1 AND | 111 WHERE import_id = $1 AND |
| 112 relation = 'waterway.bottlenecks'::regclass)` | 112 relation = 'waterway.bottlenecks'::regclass)` |
| 113 ) | 113 ) |
| 114 | 114 |
| 115 // StageDone moves the imported bottleneck out of the staging area. | 115 // StageDone moves the imported bottleneck out of the staging area. |