https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22899
--- Comment #9 from Martin Renvoize <[email protected]> --- (In reply to Martin Renvoize from comment #8) > I'm not familiar enough with the logic in this area now I'm afraid... but I > do wonder a few things: > > 1) Should it really be an ON DELETE CASCADE.. or should we be setting to > NULL or something to allow the hold to be reassigned to another item perhaps? Reminding myself now, looks like the whole table is cleared down as part of every run of the cronjob. > 2) I don't like the accessor name as above Still outstanding > 3) Should be trivial to correct the DB update to catch bad rows and clean > them up before adding the key.. but it kind of depends what the answer to > point 1 is to know what route to take (set to null or delete row) Lets go ahead and Delete -- You are receiving this mail because: 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/
