This improvement implies a change of the GeoFence DB schema, and a small
change in the API. All of this is enough to break deploy compatibility with
the existing code.
In order to underline this change, a version change is needed.
I'm going to branch master into 3.0.x, bump up the master version to 3.1.0-
SNAPSHOT and then perform the commits related to this new feature on master.
I'll also have to create a new jenkins job for the new branch.
Cheers,
Emanuele
--
GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 380 2116282
This improvement implies a change of the GeoFence DB schema, and a small
change in the API. All of this is enough to break deploy compatibility with
the existing code.
In order to underline this change, a version change is needed.
I’m going to branch master into 3.0.x, bump up the master version to 3.1.0-
SNAPSHOT and then perform the commits related to this new feature on master.
I’ll also have to create a new jenkins job for the new branch.
Cheers,
Emanuele
–
GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 380 2116282
heh, that's one area we are thinking about.
Two ways mainly:
- allow hibernate to update the schema. That should be enough to have sample
installations continue working after an update (the DB changes are only adding
a new table and related indexes). This approach may not be suitable for other
kinds of DB update anyway.
- provide migration SQL files to be applied manually between revisions. Should
be done by the DBA and requires some skills of course.
Cheers,
Emanuele
Alle 15:17:15 di Thursday 17 December 2015, Jody Garnett ha scritto:
Interesting - how do you upgrade the data base structure?
On Thu, Dec 17, 2015 at 5:59 AM Emanuele Tajariol <etj@anonymised.com>
wrote:
> Hi all,
>
> we are implementing in GeoFence the handling of the workspace
> administration
> rights; see
> - https://github.com/geoserver/geofence/issues/67
> - https://osgeo-org.atlassian.net/projects/GEOS/issues/GEOS-7350
>
> This improvement implies a change of the GeoFence DB schema, and a small
> change in the API. All of this is enough to break deploy compatibility
> with the existing code.
> In order to underline this change, a version change is needed.
> I'm going to branch master into 3.0.x, bump up the master version to
> 3.1.0- SNAPSHOT and then perform the commits related to this new feature
> on master.
>
> I'll also have to create a new jenkins job for the new branch.
>
> Cheers,
> Emanuele
>
> --
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Emanuele Tajariol
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 380 2116282
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
> -------------------------------------------------------------------------
> ----- _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 380 2116282