https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33905
--- Comment #17 from David Cook <[email protected]> --- (In reply to David Cook from comment #15) > When it comes to database triggers, we do need to be mindful of transactions > and potential database deadlocks. That said, they can be difficult to > diagnose, so easier said than done... You know... the more I think about it... the more I'm worried about this, since these triggers will fire for all updates to "borrowers", and there are a lot of different ways that borrowers can be updated (as we have 84 columns in that table). If userid and cardnumber were in a separate table, I'd be less worried. But yeah... I work on a non-Koha database with a fair number of triggers and deadlocks are a pain. Unfortunately, my concern is difficult to prove with a single user or a simple test script. It only becomes apparent when you start having concurrent users trying to modify the same data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ 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/
