Summary: | Table alert should have a FK on borrowernumber and entries be deleted with the referenced borrower | ||
---|---|---|---|
Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | ||
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: |
Description
Katrin Fischer
2013-07-23 15:53:09 UTC
Some relevant commentary from #koha: <kf> hm wondering... we delete all that, but that will make it impossible to do an 'undelete' bringing borrowers back from deletedborrowers <kf> we already delete a lot - that would make it more consistent, but I coudl imagine that might be the eaosn it was not done in the first place? <kf> i am working on a 'concept for deletion of personal data' so that's where those questions come from :) <gmcharlt> I'd rather have the FKs <kf> i will file a bug <kf> and note it for manual deletion for now... *meh* :) <gmcharlt> and if there's a desire for a more complete patron undelete, add new tables as needed <gmcharlt> e.g., deleted_borrower_alerts, etc. |