DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_suggestedbyFOREIGN KEY (suggestedby) REFERENCESborrowers(borrowernumber) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17646. DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_managedbyFOREIGN KEY (managedby) REFERENCESborrowers(borrowernumber) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17657. DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_acceptedbyFOREIGN KEY (acceptedby) REFERENCESborrowers(borrowernumber) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17669. DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_rejectedbyFOREIGN KEY (rejectedby) REFERENCESborrowers(borrowernumber) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17681. DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_biblionumberFOREIGN KEY (biblionumber) REFERENCESbiblio(biblionumber) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17693. DBD::mysql::db do failed: Incorrect date value: '0000-00-00' for column 'suggesteddate' at row 1 [for Statement "ALTER TABLE suggestions ADD CONSTRAINTsuggestions_ibfk_branchcodeFOREIGN KEY (branchcode) REFERENCESbranches(branchcode) ON DELETE SET NULL ON UPDATE CASCADE"] at /installer/data/mysql/updatedatabase.pl line 17705. This is undoubtedly due to bad data having been left behind after bug 12627. I think the most pragmatic approach is to just update any such values with a default date far in the past.
Created attachment 95850 [details] [review] Bug 24130: (RM follow-up) Fix old invalid data Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>