Thread: Calibre Sync broken by Calibre v9?
View Single Post
Old 02-05-2026, 05:04 PM   #26
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 22,277
Karma: 30317806
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by JSWolf View Post
You would not have picked up all of the database changes. The way you would have known is if you followed the calibre 9 beta thread. Plus, you had no way of knowing that calibre sync broke the rules and used part(s) of the database it should not have.
The problem with Calibre Sync and version 9 was raised in the beta test thread, see ==>> https://www.mobileread.com/forums/sh...&postcount=282

Calibre Synch broke no rules. Calibre itself and its plugins use the calibre database API which is not available on IOS and Android. Hence this app, and others like it access the metadata.db database directly. As a UK PM once said: "There Is No Alternative."

BR
BetterRed is offline   Reply With Quote