http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11623
--- Comment #1 from David White <[email protected]> --- I'll just add my own workarounds to these: * Convert everything to InnoDB prior to running the upgrade script. * Of these ALTER TABLE DROP FOREIGN KEY errors, the only one that seems to actually generate a red warning message is the patronimage one. I solved this by pre-creating the "patronimage" table with the patronimage_fk1 foreign key, so the script can happily drop it * Rewrote the /optional/ pathnames to /mandatory/ * Altered the sample_notices_message_transports.sql to delete these lines: (4, 'email', 0, 'reserves', 'HOLD') (4, 'sms', 0, 'reserves', 'HOLD') (5, 'email', 0, 'circulation', 'CHECKIN') (5, 'sms', 0, 'circulation', 'CHECKIN') (6, 'email', 0, 'circulation', 'CHECKOUT') (6, 'sms', 0, 'circulation', 'CHECKOUT') These will allow the script to run at the right time, and the 6 lines above will be created later by updatedatabase.pl later in the script anyway (when the appropriate entries in the 'letters' table have also been created). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
