Quote:
Originally Posted by chaley
A threading violation or any other error while writing the database could cause a transaction to be rolled back. How big is a transaction? My guess: changes to a column for all affected books.
|
It never happened when you changed column for multiple books, as that only fires a single event with multiple book_ids. During my testing it happened only when multiple db events where happening in succession. (e.g. adding books)
Edit: Theoretically it can happen if you bulk change multiple columns using the bulk metadata edit dialog as that fire multiple events (one event per column). But I tested this multiple times and it did not happen, but the error was random so maybe with more testing it would happen. But it was more easily replicated when adding books.