[Koha-bugs] [Bug 14698] AtomicUpdater - Keeps track of which updates have been applied to a database

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14698

--- Comment #1 from Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi> ---
Created attachment 42112
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=42112&action=edit
Bug 14698 - AtomicUpdater - Keeps track of which updates have been applied to a
database

When deploying production databases to test environments, it is imperative to
keep track of which database changes have been applied.

When one is running, in production, features that require DB changes, and want
to add more features which need more DB changes, keeping track of which updates
have been applied is challenging.
After several cycles of upgrade-deploy, with multiple atomicupdate-scripts
piling to the atomicupdates/-directory, it is impossible to easily distinguish
which updates have been applied and which are not.

Rerunning the same update scripts again and
again causes lots of noise in the upgrade log and hides real issues from being
detected.
Also repeatedly running upgrade scripts might cause bad side effects which are
potentially hard to repair.

This feature adds a script atomicupdate.pl which runs all atomicupdate/*
scripts
and .sqls and logs the event to the koha.atomicupdates-table.
On subsequent runs of atomicupdate.pl, the already deployed upgrades are
skipped, greatly reducing the unnecessary clutter and risk of upgrading.

You can also remove existing log entries to allow rerunning the same upgrade
script again, list all applied upgrades and show pending updates.

Unit tests included.

-- 
You are receiving this mail because:
You are watching all bug changes.