https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37419 Bug ID: 37419 Summary: Deleting the record source deletes the associated biblio_metadata rows. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs@lists.koha-community.org Reporter: januszop@gmail.com QA Contact: testopia@bugs.koha-community.org CC: arthur.suzuki@biblibre.com, gmcharlt@gmail.com, tomascohen@gmail.com Depends on: 35919 Blocks: 36372 After applying the Bug 36372, it is possible to manually set record source for a given bibliographic record. At the same time, from /cgi-bin/koha/admin/record_sources it is possible to delete a record source currently being used, without any control. This in turn causes the deletion of all the rows from the biblio_metadata table linked with the record source being deleted, which is fatal. BTW the biblio and biblioitems rows remain in the database. This effect is caused by "CONSTRAINT `record_metadata_fk_2` FOREIGN KEY (`record_source_id`) REFERENCES `record_sources` (`record_source_id`) ON DELETE CASCADE" in biblio_metadata setup. Of course the same effect occurs when deleting the record_sources row by hand, directly in the database. I am not sure if the decision to link biblio_metadata with record_sources with ON DELETE CASCADE is just, even if we controlled the use of the specific record source before deletion (as we do with itemtypes for instance). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35919 [Bug 35919] Add record sources CRUD https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36372 [Bug 36372] Allow privileged users to set the 'record source' on cataloguing -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.