Quote:
Originally Posted by theducks
Confirmations are there for a reason. To eliminate DB WRITE access conflicts by asking when YOU are ready (and not using those records)
CP operates in Bulk mode. 1 confirm for N books
|
Frankly, I did it in my fork and I never had any problem. This said, I do not launch any other task.
When I look back at the code, the only metadata modified are the custom columns dedicated to Count pages, and I assume the db is dealing by itself with the order of operations (queuing or locking?). I may be wrong, but for me the only problem would potentially be if you are using the columns for something else or if you are trying to modify at the same time these fields...
The fork:
here