| Summary: | Null borrowernumber in reserves table | ||
|---|---|---|---|
| Product: | Koha | Reporter: | HB-NEKLS <gwilliams> |
| Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | gmcharlt |
| Version: | 3.16 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
HB-NEKLS
2014-11-03 17:55:54 UTC
I don't see any instances in the reserves table, but I see many in old_reserves (v3.18.x). I wonder if that is the same problem. What is the effect of having holds with no borrowernumber? This was reported against a very old and now unmaintained version of Koha - 3.16. I am closing WONTFIX - please reopen if you can still see this happening in a more current version. NULL borrowernumbers in old_reserves can happen when deleting a patron: CONSTRAINT `old_reserves_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE SET NULL ON UPDATE SET NULL, In reserves the line should be deleted: CONSTRAINT `reserves_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE ON UPDATE CASCADE, |