View Single Post
Old 04-02-2017, 11:52 PM   #4
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
For example, let's take one a lot of people have, author_book_count. When the book count is updated, all the books in the library will be updated. When I next synchronize with a device, all the books will need to be resent (as then have changed since the last sync).
Actually, not true. The ABC plugin does a direct metadata.db update to the author_book_count custom column SQLite table, so it does not trigger any metadata.opf refresh. Nor should it. ABC is calculated, not a static reference metadata value. ABC also does not update the Last Modified Date for the same reason. ABC is Library-level at a specific point in time.

So, only metadata.db is changed. One file. Nothing else.


DaltonST
DaltonST is offline   Reply With Quote