[midPoint] Upgrades and version consistency

Radovan Semancik radovan.semancik at evolveum.com
Wed Jan 17 10:04:04 CET 2018


Hi,

There will be an error on startup if the database model is not 
compatible (e.g. there are missing columns). However, I would say that 
midPoint will continue to operate if the database model is compatible, 
e.g. tables were extended with additional (non-mandatory) columns.

-- 
Radovan Semancik
Software Architect
evolveum.com




On 01/16/2018 03:07 PM, Kromhout, Ethan A. wrote:
> If someone were to fail to run database upgrade scripts, but did deploy and upgrade war file in the scenario described in upgrade "Type 1" at the wiki page https://wiki.evolveum.com/display/midPoint/Upgrade+HOWTO, either through carelessness or because of a technical problem. Would the application check the database version and refuse to start, or would the error be more subtle? Is there a way to query to check that the database scripts have been run and are on the correct version?
>
> This is just a rhetorical question to clarify what might happen in different upgrade scenarios as we'll be working with some campus's on upgrade procedures and wanted to document possible failure modes.
>
> Thanks,
>
> Ethan
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint





More information about the midPoint mailing list