Quote:
Originally Posted by kovidgoyal
I am not going to be fixing this in calibre. As I have explained elsewhere metadata.db is *private to calibre*. Third party applications should not rely on it being unchanged. If an application such as calibre sync wants to use metadata.db then it is very much on it to ensure it handles changes to the database schema. Indeed given that calibre sync appears to be unmaintained, I would discourage anyone from relying on it since as metadata.db and other parts of calibre change over time, it is quite likely calibre sync will either break or worse corrupt data.
|
Thanks a ton for clarifying things out @kovidgoyal, this saves folks in this thread from waiting for Calibre or Calibre Sync updates that would fix the issue. I guess you are also dissuading us from manually altering the Calibre DB or doing a rollback to version 8.x.
This leaves me a bit concerned about the future of Android companions apps to Calibre, as no actively maintained project seems to currently exist. It is a bit of a missed opportunity; with the death of CS and Calibre Companion (have not yet tried JetReader which is in alpha I think), there is clearly a vacuum as many e‑reader manufacturers move to platforms that allow APK side-loading and/or provide Google Play access.
Accessing Calibre‑synced cloud files directly on my e‑reader is extremely convenient and suits my reading workflow best. Alternatives (I mainly use Dropsync) either require input on your main PC or to sync everything, which is not feasible/reasonable for even medium-sized digital libraries. The in-built Calibre server is truly excellent, but many institutions (like my uni) limit port opening/tunneling on their networks, so I can't easily access my books' catalogue remotely from my e-ink devices.
Just my two cents, but without a viable companion app, Android e-readers with a remote Calibre integration cannot be leveraged to their full potential...