[midPoint] Upgrades and version consistency

[Wojciech Staszewski]

Hello!

This is a great idea.
I'm using software where the update is handled beautifuly.

First, database is versioned.

Second, The SQL update script lifts up the db version after each correctly ended query.
If the update script is finished OK, the database is in version XXX.
If the update failed for some reason (eg. DB tables partitioning), I know exactly which step failed and after I fix the problem I can run whole script once again and
it starts from the failed step.

Third: DB version is checked on application startup. Application won't run if DB version is incorrect.

Simple and nerve-saving. I'd like to see something like that in MP.

Regards,
WS

W dniu 16.01.2018 o 15:07, Kromhout, Ethan A. pisze:
> 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
>