[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
Mon Jul 3 10:39:52 CEST 2023


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

--- Comment #9 from Julian Maurice <julian.maurice at biblibre.com> ---
The goal is to reduce manual work.

RM/RMaint won't need to rename the file and update the version number. There
will be no distinction between a "dev update" (located in atomicupdate
directory) and a "prod update" (located in db_revs directory). It becomes just
like any other piece of code: it doesn't need to be moved once
pushed/backported.

Also DB updates will never be executed twice (currently this can happen when
switching from a stable version to another, since DB updates are often
backported) so they won't need to be idempotent and should be easier to write.
For instance there is no need to check if a column exists before adding it
because that column cannot exist before the update was executed.

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


More information about the Koha-bugs mailing list