[Koha-bugs] [Bug 27880] Store each database migrations state in database

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Jul 11 03:01:28 CEST 2023


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27880

--- Comment #34 from David Cook <dcook at prosentient.com.au> ---
Looking at backported db_revs and I think it is like Julian says. 

The following two files are equivalent:
./installer/data/mysql/db_revs/221102001.pl
./installer/data/mysql/db_revs/221200004.pl

When you upgrade from 22.11.03 to 23.05.03, you will run
./installer/data/mysql/db_revs/221200004.pl even though
./installer/data/mysql/db_revs/221102001.pl has already run.

The database migration system actually should be better because you're less
likely to run the same migration script twice. 

The migration for "./installer/data/mysql/db_revs/221102001.pl" would be pushed
to master then backported to 22.11.03. You run it as part of 22.11.03, which
means you don't run it again when you're upgrading to 23.05.03. Nice.

--

The only issue would be if there's a migration in 23.05.03 which conflicts with
the database coming from 22.11.03, but that would already be a problem with
updatedatabase.pl and db_revs anyways.

--

So overall I think it should be OK in that respect.

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


More information about the Koha-bugs mailing list