https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33972
--- Comment #5 from Nick Clemens <[email protected]> --- Also see 33987 - similar deadlock when accessing the same import record row multiple times I can say, I can't reproduce in KTD, but I can replicate every time on our production servers. In terms of setting the status, doing so twice in a transaction doesn't make sense. It will revert to the original if it fails, or use the final if it succeeds. Moving the first one made sense because then the status will be left at 'importing' - the job should be 'failed' so we know there is a problem? Here and on 33987 I think the code makes sense on its own, even if the problem doesn't always occur -- You are receiving this mail because: 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/
