#88: enhancements ideas for mapbender_setup
--------------------------+-------------------------------------------------
Reporter: Marko | Owner: [email protected]
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: installation | Version: 2.4.2
Keywords: setup |
--------------------------+-------------------------------------------------
-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.
like:
{{{#--------------------}}}[[BR]]
{{{#Mapbender Version }}}[[BR]]
{{{#--------------------}}}[[BR]]
{{{define("MB_VERSION", "2.5.0");}}}
-The future mapbender-setup '''update function''' should get the required
database changes from a historized '''database-changes file'''
(txt,xml,json ...whatever?!) to update and the installed Mapbender
Algorithm Idea:[[BR]]
{{{current version 2.4.0<->new version 2.5.0}}}[[BR]]
{{{=> create an update script from version 2.4.1 up to 2.5.0 from
database-changes file ......}}}
database-changes file structure:[[BR]]
{{{<version>2.4.1</version>}}}
{{{<change>CREATE TABLE layer_epsg_tmp AS SELECT DISTINCT * FROM
layer_epsg;</change>......}}}[[BR]]
{{{<version>2.5.0</version>}}}
{{{<change>ALTER TABLE wfs_conf_element ADD COLUMN f_auth_varname
VARCHAR(50);</change>......}}}[[BR]]
--
Ticket URL: <http://trac.osgeo.org/mapbender/ticket/88>
Mapbender <http://www.mapbender.org/>
Mapbender_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
