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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Oct 9 01:08:57 CEST 2020


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

Agustín Moyano <agustinmoyano at theke.io> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |agustinmoyano at theke.io

--- Comment #10 from Agustín Moyano <agustinmoyano at theke.io> ---
I agree there should be a consistent way to stop the upgrade process, and
specially one that will allow to resume from the place it broke, but I think we
should try to stop the upgrade process as little as possible.. 

meaning that for example if we add a FK on a nullable column, and there are
some values that don't exists in the foreign table, instead of killing the
process, we can copy the offending rows to some table we create, set the column
to null, add the restriction and raise a warning..

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


More information about the Koha-bugs mailing list