https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27880
--- Comment #37 from David Cook <[email protected]> --- (In reply to Julian Maurice from comment #36) > (In reply to David Cook from comment #35) > > If we move it to the start of the application, I think we'd have to process > > upgrades automatically behind the scenes and not via the UI. > > It's an interesting option. But maybe Koha should warn before making changes > to the database schema. Or administrators should be able to disable this > feature if they want greater control. > Another option is to simply refuse to start and tell the administrator it > should run updatedatabase.pl > Another one is to start a minimal app that includes only the web installer > (but that would probably require another restart after the web installer is > done). I suppose another option would be to do the install/upgrade check at startup time and set a variable in a global/singleton like Koha::Installer, which would be checked by each worker... If "need_upgrade" is set, then they repeat the check, because only 1 worker will likely complete the install/upgrade process, and the other workers would be working with stale data... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
