Quote:
Originally Posted by Quoth
I personally only care about annotations FROM the Kobo to PC via Kobo Utilities, which are saved in plain text files.
|
Are they automatically exported? How do you do that? I thought I had somehow managed to configure something for that because I have 2 annotations .txt files in the kobo memory that I do not remember manually exporting, but only 2, when I have annotated many many more books than 2. I vaguely remember activating an option in the conf file (I think?) to allow exporting annotations but as far as I can tell it must be done manually from inside the book and if you open a book to export the annotations the datestamp is reset which ruins my sort order so it's not ideal. Plus I have to remember to do it.
Quote:
Originally Posted by Quoth
You could note current % read for any open books. I did that for a couple of books the time I loaded an earlier backup of the database when it broke (rare). Obviously a backed up database has nothing about what you did since.
|
I think / hope I have noted current % read for open books, using the plugin. I also have saved "date" but I think that only concerns the date the book was opened, not the date it was sent to the device, unfortunately. I open books sometimes to move them to the top of the list, and I also deliberately don't finish a book to the last page sometimes if there is something in it I want to remember to check. Plus the books I am actually currently reading. So I don't want to lose that information if I can avoid it.
Quote:
Originally Posted by PeterT
It's quite possible that if the index is damaged or the database lacks consistency that it will be impossible to delete a row.
|
It might be user error. I am attempting to learn how to manage databases as I go along here so I am just blindly trying things and hoping they work. But certainly some / a lot of things are not working as I would expect. Almost nothing is working in fact. :/
Quote:
Originally Posted by davidfor
I think the main issue is the error in "sqlite_autoindex_content_1". The unique constraint error is because there are two rows in the "content" table with the same value in the "ContentID" column. That, of course, shouldn't happen. The content table contains the details of all the books on the device. There is one row for every book plus rows for each ToC entry in the books (with some complications). Removing the book that is causing the problem might fix it.
You should be able to find the book by running the SQL statement:
Code:
SELECT ContentId, COUNT(*)
FROM content
GROUP BY ContentId
HAVING COUNT(*) > 1
That will hopefully produce one result for the book causing the problem. The ContentId will tell us which book it is. It should start with "/mnt/onboard". If you are using calibre to sideload, then I'd expect it to look something like:
Code:
file:///mnt/onboard/Testing/Fussell, Paul/Great War and Modern Memory, The - Paul Fussell.kepub.epub
The title and author are in that and you can find it and delete it in the device. Or, find it in when the device is connected and delete it. If you do that, when you disconnect, the device should detect the missing book and remove it. |
That makes sense. I tried running the statement you gave me but the result said "no data to display" (see screencap attached). I don't know why. There very clearly should be data to display.
I accidentally ran it once halfway through (only the first 2 lines) and that did give one result, so I deleted that book and all associated files with the same filename (some images, and annotations file...), but this did not fix the problem.
Quote:
Originally Posted by davidfor
If you are saving the reading status, the can be restored to the device. Collections can be maintained through the driver. If you are doing this manually, then you can get the collections from the device and store them in calibre and then restore them later.
The annotations can be fetched using the Annotations plugin, but, they can't be restored. There isn't enough information stored to be able to do this. They are stored in the database and the table can be manually copied with a bit of work.
|
I set the plugin to save everything there was an option for (4 columns) so if reading status is one of those it is saved. I know Collections are saved. Is it possible to restore the datestamp as well, for sorting by "Recent"? I have the Annotations plugin, it saves the annotations to a custom column, but I would prefer to have them on the device as well ideally. How complicated is it to manually copy a table?
Today the problem is worse:
Database check
I don't know why, and although I copied the database from yesterday with only the one error back to the device the new errors reappear each time after I eject / reconnect.
At this point I am not sure it is possible for me given my lack of database skills to correct this problem. I have not managed to do any of the things suggested, the problem is getting worse, and I am getting pretty frustrated. I think it's probably best if I try to salvage as much as I can and just start fresh with a new database, much as it annoys me.
This is my first experience with a device that uses a database, my previous devices (Sony and Cybook) did not work that way as far as I know, and although I have been mostly happy with the Kobo so far this is really putting a damper on my enthusiasm, I never had any problem even remotely like this with the others.