Calibre Sync broken by Calibre v9?

[dizzy274]

Originally Posted by VelvetElvis

Updated to Calibre 9, and now Calibre Sync is failing to update on any of our tablets, with the error shown below. Not sure if it's related to the Calibre update or not

Anyone else having issues updating Calibre Sync, or know of the cause? Sent the developer an email but have not heard back.

Hi,

I'm having exactly the same problem, I sent a request and example to Calibre Sync over the weekend, but I've not had an acknowledgement or reply. I've started to hit other problems with Calibre Sync in the last few days as well. They're not responsive like they used be.

Guess I'll give it a while to see if there's any response before trying workarounds as who knows what else has been screwed up and a workaround might cause more problems if the original problem is fixed, not a good situation.

Best Regards.

Ian.

[VelvetElvis]

Originally Posted by dizzy274

Hi,

I'm having exactly the same problem, I sent a request and example to Calibre Sync over the weekend, but I've not had an acknowledgement or reply. I've started to hit other problems with Calibre Sync in the last few days as well. They're not responsive like they used be.

I too sent a request for support. No response, but maybe understandable if he's been inundated with requests.

But you're right - At the beginning the dev was super responsive, adding requested features and fixing bugs quickly. But about a year ago I sent a query regarding adding a sort feature to the downloaded book view that persisted after restarts. Got a response after my second email, where he expressed no interest in doing it.

His website, under "What's New", hasn't been updated since the beginning of 2024. Hoping this app doesn't go the way of Calibre Companion.

[dizzy274]

Originally Posted by VelvetElvis

I too sent a request for support. No response, but maybe understandable if he's been inundated with requests.

But you're right - At the beginning the dev was super responsive, adding requested features and fixing bugs quickly. But about a year ago I sent a query regarding adding a sort feature to the downloaded book view that persisted after restarts. Got a response after my second email, where he expressed no interest in doing it.

His website, under "What's New", hasn't been updated since the beginning of 2024. Hoping this app doesn't go the way of Calibre Companion.

I fear the worst, I hope I'm wrong but it's showing all the signs of abandonware.

Another gotcha is, that unless you've got a pre 9.0 copy of the Calibre database I wouldn't expect to be able to revert to Calibre 8, Calibre would have exactly the same problems Sync is having with the different database structure, you'd have to do both, wouldn't you?

[JSWolf]

Originally Posted by dizzy274

I fear the worst, I hope I'm wrong but it's showing all the signs of abandonware.

Another gotcha is, that unless you've got a pre 9.0 copy of the Calibre database I wouldn't expect to be able to revert to Calibre 8, Calibre would have exactly the same problems Sync is having with the different database structure, you'd have to do both, wouldn't you?

If going back fails, then what you can do is with 8.16.2, with a copy of the library, rebuild the database.

[BetterRed]

Originally Posted by dizzy274

Another gotcha is, that unless you've got a pre 9.0 copy of the Calibre database I wouldn't expect to be able to revert to Calibre 8, Calibre would have exactly the same problems Sync is having with the different database structure, you'd have to do both, wouldn't you?

Very limited tests suggest calibre 8.16.2 can cope with a database created and updated by calibre 9.1 including user defined custom columns… it didn't use the three deleted columns, so the lack thereof should not matter.

I would recommend the 'book-pages_link' table be dropped… then, when and if you upgrade to version 9.x, calibre will create it… according to the then current definition.

Just make sure you have and maintain adequate backups.

BR

[rantanplan]

Originally Posted by BetterRed

Very limited tests suggest calibre 8.16.2 can cope with a database created and updated by calibre 9.1 including user defined custom columns… it didn't use the three deleted columns, so the lack thereof should not matter.

I remember Kovid posting somewhere, that the three columns weren't used for a long time, which is why they were dropped now.

[dizzy274]

Originally Posted by JSWolf

If going back fails, then what you can do is with 8.16.2, with a copy of the library, rebuild the database.

Yes that would work, wouldn't it. In fact I think I'd rather do that than hope 8 works with a 9 database.

Best Regards.

Ian.

[dizzy274]

Originally Posted by VelvetElvis

Updated to Calibre 9, and now Calibre Sync is failing to update on any of our tablets, with the error shown below. Not sure if it's related to the Calibre update or not

Anyone else having issues updating Calibre Sync, or know of the cause? Sent the developer an email but have not heard back.

I don't know if you know...., but someone emailed the Developer about the error on 10th of January, so I guess we're not going to get a fix. I use Calibre quite a lot, but I don't use many of its facilities, so reverting to 8 wouldn't really concern me. I always ran the updates when they were offered without bothering too much about what the update was for, perhaps if I'd studied the changelog, I would have picked up the DB change,

Best Regards,

Ian

[JSWolf]

Originally Posted by dizzy274

I don't know if you know...., but someone emailed the Developer about the error on 10th of January, so I guess we're not going to get a fix. I use Calibre quite a lot, but I don't use many of its facilities, so reverting to 8 wouldn't really concern me. I always ran the updates when they were offered without bothering too much about what the update was for, perhaps if I'd studied the changelog, I would have picked up the DB change,

Best Regards,

Ian

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.

[Loosheesh]

Originally Posted by dizzy274

I don't know if you know...., but someone emailed the Developer about the error on 10th of January, so I guess we're not going to get a fix. I use Calibre quite a lot, but I don't use many of its facilities, so reverting to 8 wouldn't really concern me. I always ran the updates when they were offered without bothering too much about what the update was for, perhaps if I'd studied the changelog, I would have picked up the DB change,

Best Regards,

Ian

The thing that saved me is my paranoia with new updates. With every update, even incremental ones, I get anxious my Calibre will get broken. With major updates I usually dither for ages and come here frequently to see how it's affecting other people before I take the plunge.

I'm still hoping Calibre Sync fixes the problem soon, otherwise I won't be able to update Calibre in the near future.

[BetterRed]

Originally Posted by JSWolf

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

[JSWolf]

Originally Posted by BetterRed

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

Well, because CS used bits of the database that calibre didn't use, it's now broken because the database has been cleaned up.

[slm]

Originally Posted by BetterRed

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

Actually, for most purposes, there is an alternative. If you have access to the database, you probably have access to (a copy of) the Calibre library itself. You can reconstruct the main parts of the Calibre database from the directory structure, the metadata.opf files and related files. While it doubtless misses some of the newer features of Calibre, the actual file structure was designed so the Calibre's database could be reconstructed from it. Older versions of the Calibre library maintenance routine basically did this walkthrough.

This approach works on an Android or iOS device that has access to the library--I use a quick-and-dirty version of the directory walk for a personal program. The problem is that truly reconstructing the Calibre info this way is very slow.

[BetterRed]

For a large library, it would quicker to copy the v9'd database somewhere safe, then alter the books table to reinstate the isbn, lccn and flags columns and drop the books_page_links table.

Should be scriptable.

BR

[PeterT]

I've taken the step of editing my review in the Android Play Store to give a one star rating and adding in the fact that it's not compatible with calibre 9.x.

Sent from my Pixel 9a using Tapatalk