[davidfor]

Originally Posted by theonna

Then why Calibre does not create Kobo database? It seems that it would be more efficient not to require Kobo to process new books, if Calibre could just create the database?

The Kobo driver will create the appropriate database entries for the shelves, and modify the rows that describe the books, but it doesn't create these rows. Why? Because I'm chicken. I've looked at the database rows needed and I have worked out most of what Kobo has put into them. But, there are some values I am not sure of. I have tried and when I compared what I had with what the device created, it wasn't quite right. Plus, it is a moving target. Kobo do change the database and exactly how the books are defined over time. Overall, it isn't worth it. Someone else has tried, and gave up fairly quickly.

Also for Kindle - file describing collections, only describes collections, if case of corruption, you only loose collection information. For Kobo database corruption will cost you more, because you would need to relog, then resync and reprocess all your books. So unless you are absolutely sure what your are doing you probably don't want to mess with SQLite editing Kobo database. In short there is no manual, and it is not a userfriendly task.

Yep, manually editing the database is not for everyone. But, it would not be very hard to create a script that would be safe. In fact, a few different ones have been posted here.