http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9011
--- Comment #13 from Jonathan Druart <[email protected]> --- (In reply to comment #12) > (In reply to comment #11) > > You should add a "on delete cascade" option (set null ?) or remove this > > constraint. > > It is a dilemma: in one case we loose the information, in other one we loose > > the constraint :-/ > Not cascade, but set null, I don't see the dilemna: with cascade, you delete > the item if the borrower is deleted. This is bad :\ Yes, not cascade, of course. But with set NULL, we loose the information. If the borrowernumber is kept in the last_returned_by field, we can retrieve it using the deletedborrowers table. -- 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/
