Summary: | Add primary, foreign keys to statistics table | ||
---|---|---|---|
Product: | Koha | Reporter: | Barton Chittenden <barton> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, kyle.m.hall, lari.taskula, martin.renvoize |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 5334 |
Description
Barton Chittenden
2017-04-17 23:18:14 UTC
+1 I think sometimes it's really useful that the entries are not all 'NULLed' on deletion of an item, borrower or staff user. Especially with our current 2 table setup. I often have to dig in statistics and action_logs when "strange things" happen at the circulation desk. Maybe insted of a FK we could just add an index? (In reply to Katrin Fischer from comment #2) > I think sometimes it's really useful that the entries are not all 'NULLed' > on deletion of an item, borrower or staff user. Especially with our current > 2 table setup. I often have to dig in statistics and action_logs when > "strange things" happen at the circulation desk. > > Maybe insted of a FK we could just add an index? Never got a reply here. Marking WONTFIX, please re-open if you disagree. In this case I agree, I don't think I'd use a foreign key but I see no issue with adding indexes for performance. |