View Single Post
Old 09-14-2021, 08:29 AM   #702
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,200
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Quote:
Originally Posted by capink View Post
I think I have a solution for this now. I will add a hibernation mode for the Last Modified plugin, which can be activated by other plugins. During this hibernation period, the plugin will listen to and cache db events without taking any action. After getting out of the hibernation mode, it will re-emit one db event per field (for all books) to enhance performance.

This will need modifications to both Last Modified and Action Chains, and will only be released after the release of the next version of calibre.

@chaley: How can I incorporate the advice below with set_field()

Quote:
Originally Posted by chaley View Post
But with auto-commit turned off so the transactions are grouped into one commit.
capink is offline   Reply With Quote