[Koha-bugs] [Bug 25078] Gracefully stop updatedatabase/installer when a database change cannot be applied

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

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

Julian Maurice <julian.maurice at biblibre.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |julian.maurice at biblibre.com

--- Comment #24 from Julian Maurice <julian.maurice at biblibre.com> ---
I suggest to go even further by removing the tie between Koha version and
database updates. It is not needed that each database update increments the
Koha version (and it gives RM/RMaints additional work that could be avoided).

I wrote something with that idea in mind:
https://gitlab.com/jajm/Koha/-/commits/migrations -
https://gitlab.com/jajm/Koha/-/commit/58bb8addbd4bb8deedd4643b8c465d8ac1857d8f

Basically it's like atomicupdate, but the filename is prefixed by a timestamp
to keep the updates ordered and the filename is saved in a table once
successfully executed (so that updates are not executed twice).
No need to replace XXX by the correct version, and it should be
backport-friendly (but only once this get pushed into stable releases... can't
win everywhere :/)

This makes the 'Version' system preference useless, so a lot of the patch is
for removing usage of it.

I realize that it's out of the scope of the current bug, but since other
patches tend to go that way (splitting DB updates), I think that having another
alternative is good for discussion.

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