https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33905 --- Comment #23 from David Cook <dcook@prosentient.com.au> --- (In reply to David Cook from comment #22)
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.
In theory... it should be a rare event that NEW.cardnumber and NEW.userid is not null for a borrowers table change, which means that the subqueries shouldn't run? You know... it'll probably be fine. The deadlocks I get on other systems are high-write high-concurrency systems. I guess I'm just trying to think of any possible pitfalls. But maybe let's not have the perfect be the enemy of the good... -- In which case, I think overall this looks pretty good. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.