https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33905
--- Comment #22 from David Cook <[email protected]> --- (In reply to Tomás Cohen Arazi (tcohen) from comment #21) > > But... that would also be a big breaking change... > > We are now having THE conversation, and we know how it looks to use the > triggers. I will give the separate table a try tomorrow Well... I thought I was on-board for the database trigger, but now I'm having doubts. We could try the "borrower_identifiers" option, and reset userid wherever it matches a cardnumber. In theory, that should work, and it shouldn't actually break anything... because the identifier itself will be preserved in someone's cardnumber. But it would be a significant change. Maybe we just try out the DB trigger based solution, since it's easy to add, and if it is a problem - it's also easy to remove. -- 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/
