![]() In the most bad scenario (a library that I shared with another person an we both had calibre open at the same time and added/deleted books in the same sesion) I had to restore the database, a thing that took a while but resolved the issues. The tools in Library maintenance usually helped me with the issues. And by problems I mean that books that are in the folder structure don't appear in Calibre (so the books are there but are not seen). If you don't add or delete books but just read, the problems are minimal and the tools in calibre can fix the database. And you have to close calibre when you don't use it, or when you close your computer (some mistakes where made when I just put the laptop to sleep whit calibre open and then open calibre on another computer or laptop). At first, I tried to upload my ebooks to Kindle service, but not all books (larger ones) would fit to the service and after some time, I had a mess on my hands, because books would be across devices and directories. I have so many books, but my organization is zero. The problems appear mostly when you add or delete books (again if you don't wait for the sync). I have a huge problem I had to address long time ago. Usually is a metadata.db and if you have full text search enabled and you added some books then is full-text-search.db also. So to summarize the possible problem, if you open calibre on one computer an plan to open it after on the other: before closing the first, make sure the onedrive finished the sync with the cloud then before open the calibre on the other computer, wait for the onedrive to finish the sync. Even if you don't actually do an annotation the file is still modified. ![]() Annotations are now written directly in the epub file. ![]() With the annotations on epubs can be another problem (if you don't wait for the sync to be over before opening calibre). The books are not suffering but the metadata and databases can have problems (multiple versions). I have 3 computers that access a big library on ondrive and only had issues when the sync is not done before opening calibre. The only thing that is a problem is when you don't wait for the sync to finish. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |