Reflect database model changes for SQL views in backend In principle, we could use many datasources with different database schemas, but this would imply changing GeoServer initialization, service filtering, endpoints and eventually more. Since we do not need it, just hard-code the schema name as a constant.

teichmann@intevation.de = sascha.teichmann@intevation.de
bernhard.reiter@intevation.de = bernhard@intevation.de