comparison pkg/imports/config.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 807569b08513
children 25967829cf00
comparison
equal deleted inserted replaced
1994:a7c4005b723f 1995:59055c8301df
104 username, 104 username,
105 kind, 105 kind,
106 send_email, 106 send_email,
107 cron, 107 cron,
108 url 108 url
109 FROM waterway.import_configuration 109 FROM import.import_configuration
110 WHERE id = $1` 110 WHERE id = $1`
111 111
112 loadConfigAttributesSQL = ` 112 loadConfigAttributesSQL = `
113 SELECT k, v 113 SELECT k, v
114 FROM waterway.import_configuration_attributes 114 FROM import.import_configuration_attributes
115 WHERE import_configuration_id = $1` 115 WHERE import_configuration_id = $1`
116 ) 116 )
117 117
118 // LoadIDConfigContext loads an import configuration from database. 118 // LoadIDConfigContext loads an import configuration from database.
119 func LoadIDConfigContext(ctx context.Context, conn *sql.Conn, id int64) (*IDConfig, error) { 119 func LoadIDConfigContext(ctx context.Context, conn *sql.Conn, id int64) (*IDConfig, error) {