Quote:
Originally Posted by Starson17
Great! That's what I need.
|
The fact that it worked bothered me. I know that calibre caches book data in memory. The cache should prevent the content server from seeing database changes, but it clearly does see them. After some poking around, I found that if the content server is running separately from the GUI, then it checks the modification time of the DB on each web request. If the DB has been changed, the content server refreshes its in-memory caches before processing the request.
Clearly Kovid anticipated running the content server on a DB that can change.
It is nice knowing that something works by design instead of by accident.