https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32729
Lari Strand <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Lari Strand <[email protected]> --- (In reply to Cab Vinton from comment #1) > Unless there's a good reason for this data loss, the itemnumber should be > preserved. I agree. We need this information for reports and finding out biblio details based on the itemnumber in the old_issues table etc. I propose we remove the constraint: CONSTRAINT `old_issues_ibfk_2` FOREIGN KEY (`itemnumber`) REFERENCES `items` (`itemnumber`) ON DELETE SET NULL ON UPDATE SET NULL, from old_issues-table. Same goes for old_reserves-table (propably should make a new ticket?): CONSTRAINT `old_reserves_ibfk_3` FOREIGN KEY (`itemnumber`) REFERENCES `items` (`itemnumber`) ON DELETE SET NULL ON UPDATE SET NULL, These tables are archive tables and I think this information should be preserved. I can't justify the data loss with any good reason. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
