Christoph Baudson (WhereGroup) schrieb:
The update process is very painful at the moment. I start this thread
to gather where things go wrong. Please add, so we can find out what
we have to improve.
Example: in Mapbender 2.5 we have a new table gui_wfs_conf. In the
current update script we have a line like this
INSERT INTO gui_wfs_conf (fkey_gui_id, fkey_wfs_conf_id) VALUES
('gui_digitize', 1);
which links the GUI "gui_digitize" to wfs_conf with Id 1. This is done
to restrict access to this WFS conf to users who have access to
"gui_digitize".
Of course, an update SQL should link "all" GUIs that use configured
WFS. As far as I can see, we would need to check the element vars for
wfs_conf_id_string, see if the wfs conf id is listed, and then link
them. Tricky, at least in SQL.
Another problem are configuration files. If there are new entries, how
do they get into existing conf files?
For example, Mapbender 2.5 will have new variables in "wfs_default.conf"
and "digitize_default.conf".
--
_______________________________________
W h e r e G r o u p GmbH & Co. KG
Siemensstraße 8
53121 Bonn
Germany
Christoph Baudson
Anwendungsentwickler
Fon: +49 (0)228 / 90 90 38 - 25
Fax: +49 (0)228 / 90 90 38 - 11
[EMAIL PROTECTED]
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
_______________________________________
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Arnulf Christl, Olaf Knopp, Peter Stamm
_______________________________________
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
