Hi devs,
Astroid, sorry, Astrid and me just had a little mail-conference about the
mapbender_setup.php.
Summary of our thoughts:
For the current mapbender_setup and the further development, it would be nice
to have a version number at one central point, like the mapbender.conf.
For the curent version, just for displaying it at the mapbender_setup.
For further version, to create a dynamic update script for the installed
version. (for example)
Example:
1. mapbender.conf has version 2.4.0
2. mapbender.conf-dist has version 2.5.0 (or furture mapbender-setup script has
the latest version number hardcoded)
3.The future mapbender-setup update function will get the required database
changes from a historized database-changes file (txt,xml,json ...whatever?!)
current version 2.4.0<->new version 2.5.0 = create an update script from
version 2.4.1 up to 2.5.0 from database-changes file ......
<version 2.4.1 changes>
<CREATE TABLE layer_epsg_tmp AS SELECT DISTINCT * FROM
layer_epsg;>......
<version 2.5.0 changes>
<ALTER TABLE wfs_conf_element ADD COLUMN f_auth_varname
VARCHAR(50);>......
4. run script
5. and so on
What do you think about a version number at the conf?
What do you think about the idea for expand the mapbender_setup of mapbender
with an update function? Any ideas or thoughts?!
Greetings,
Marko Samson
Marko Samson
Landesbetrieb Wald und Holz NRW
GIS-Anwendungsentwicklung
Referat I-5
Albrecht-Thaer-Straße 34
48147 Münster
Tel.: 0251/91797 - 169
Mail: [EMAIL PROTECTED]
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
