https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25078
Agustín Moyano <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #10 from Agustín Moyano <[email protected]> --- 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. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
