Mercurial > gemma
comparison pkg/scheduler/boot.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 | 8bbdad3f9af7 |
| children | c06a2e5397fc |
comparison
equal
deleted
inserted
replaced
| 1994:a7c4005b723f | 1995:59055c8301df |
|---|---|
| 25 const ( | 25 const ( |
| 26 bootRole = "sys_admin" | 26 bootRole = "sys_admin" |
| 27 | 27 |
| 28 selectImportConfSQL = ` | 28 selectImportConfSQL = ` |
| 29 SELECT id, username, cron | 29 SELECT id, username, cron |
| 30 FROM waterway.import_configuration | 30 FROM import.import_configuration |
| 31 WHERE cron IS NOT NULL` | 31 WHERE cron IS NOT NULL` |
| 32 | 32 |
| 33 scheduledIDsSQL = ` | 33 scheduledIDsSQL = ` |
| 34 SELECT id from waterway.import_configuration | 34 SELECT id from import.import_configuration |
| 35 WHERE username = $1 AND cron IS NOT NULL` | 35 WHERE username = $1 AND cron IS NOT NULL` |
| 36 ) | 36 ) |
| 37 | 37 |
| 38 func init() { go boot() } | 38 func init() { go boot() } |
| 39 | 39 |