Error when switching libraries

[gers1978]

Tonight I consolidated 5 libraries into 1, and intended to use the Virtual Library feature more often. I left 1 blank library called Test, for testing conversions, etc.

However now when I switch between the 2 libraries I have left, I get the following error:


calibre, version 0.9.32
ERROR: Unhandled exception: <b>ValueError</b>:389 is not in list

Traceback (most recent call last):
File "site-packages/calibre/gui2/dialogs/quickview.py", line 137, in book_was_changed
File "site-packages/calibre/library/caches.py", line 946, in row
File "site-packages/calibre/library/caches.py", line 943, in index
ValueError: 389 is not in list


Running 0.9.32 on OS X 10.8.3.

[BetterRed]

Originally Posted by gers1978

Tonight I consolidated 5 libraries into 1, and intended to use the Virtual Library feature more often. I left 1 blank library called Test, for testing conversions, etc.

However now when I switch between the 2 libraries I have left, I get the following error:


calibre, version 0.9.32
ERROR: Unhandled exception: <b>ValueError</b>:389 is not in list

Traceback (most recent call last):
File "site-packages/calibre/gui2/dialogs/quickview.py", line 137, in book_was_changed
File "site-packages/calibre/library/caches.py", line 946, in row
File "site-packages/calibre/library/caches.py", line 943, in index
ValueError: 389 is not in list


Running 0.9.32 on OS X 10.8.3.

Here's some ideas

First ensure you have a backup of your main library

If your Test library is an one of your old ones, now empty and renamed, then I suggest removing it from Calibre and deleting it from your file system and then creating a fresh Test library based on your existing library.

Otherwise, run Check Library on the Main Library - it has two phases, first it checks database integrity then it offers to check for inconsistencies between the database and book folders.

I've never had a database integrity check return error, but if I did then I would use the Restore database option. This recreates the database from the opf files in the book folders - that's why they're there.

I wouldn't have thought that database/folder integrity would cause this sort of error, but if there are any then its probably a good idea to resolve them.

If that doesn't fix it, then I'm guessing that 389 is a Calibre book_id.

I don't know if there's an 'official way' to determine what book 389 is, but I would use the SQLite Browser program to look at the books table in metadata.db.

Another way might be to use Spotlight to look for a folder with a 389 in its name

Then I'd copy book 389's folder to a safe place, then I'd remove it from Calibre. Then I'd try the library switch, if it works then I would add the book again from its safe place. Just add the format files and the cover, then update the metadata in the 'normal' way.

Otherwise I've run out of ideas.


If I was amalgamating libraries, I'd run Check Library and resolve any issues on each of them before doing the amalgamation.

I would also use the Library Duplicates feature of the Find Duplicates plugin to ensure that the 2nd-nth library I amalgamated did not have any duplicate books. If there were any I'd move them to another library called Duplicates that I would 'sort out' once I'd moved everything else.

BR

[kovidgoyal]

Close the quickview window and restart calibre.

[chaley]

I have submitted code changes to prevent this exception. The fix should be in the next calibre release.