Sounds good to me.
Is there a time when older versions will be taken out of updatedatabase.pl? At the moment, updatedatabase.pl is over 20,000 lines long. Maybe we could move the old entries into a 3to2105.pl script?
David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Jonathan Druart
Sent: Tuesday, 17 August 2021 7:17 PM
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Improvement of our upgrade process
Hi devs,
Bug 25078 was pushed yesterday and it modifies how we deal with our upgrade process.
I adjusted the wiki page - https://wiki.koha-community.org/wiki/Database_updates
The different things to know about it:
* The skeleton for atomic updates is modified [1]
* On push the atomic updates are no longer appended to updatedatabase.pl but moved to a new db_revs directory (named by version, like 210600016.pl for the entry 21.06.00.016)
* Versions from 21.06.00.000 have been migrated to use this new mechanism, older are still in updatabase.pl
* updatabase.pl is still the script to call if you want to upgrade the DB
* Each DB rev (and atomic update) is executed in a transaction that rollbacks and stop the upgrade process if something went wrong
* Old atomicupdate format will still work (but require more work for the RM)
* Better error handling and better warnings possible
* Nicer UI during the upgrade step (step3)
Let me know if you have any questions!
Cheers,
Jonathan