View Single Post
Old 02-07-2026, 09:04 PM   #4
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,992
Karma: 29579720
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
That works when metadata.db is corrupted and cant be opened, and continues to work to this day.

Once you start modifying metadata.db outside of calibre you can do pretty much anything including changing data and those changes will propagate to the distributed backups, leading to the above mentioned total data loss. Simply *never* modify metadata.db outside of calibre. metadata.db is *internal to calibre*. And calibre has *never* been robust against users messing with metadata.db directly and never will be.
kovidgoyal is offline   Reply With Quote