View Single Post
Old 09-12-2015, 11:17 PM   #10
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
calibre-server will only ever write to the database when performing an automatic schema upgrade after a calibre update changes the layout of the database... which happens only rarely.

If you really want to prevent the database from being modified, you could always use the environment variable "CALIBRE_OVERRIDE_DATABASE_PATH" pointed at a temporary copy which can be trashed.
Don't modify any metadata while you do this calibre might lose track of your books!
eschwartz is offline   Reply With Quote