Quote:
Originally Posted by chaley
FWIW I have been working with Kovid on calibre for more than 10 years, including in the database layer. I have some idea of what I am talking about.
Calibre loads the DB into memory when it starts. If you make changes it starts with the memory copy, changes it, then writes it to the DB. It does not check if the DB had been changed. If another calibre instance is running then the two memory copies are now out of sync. Changes in the other instance will overwrite those made by the first instance. For a certain class of changes the result will be a database that is not consistent with the rest of the library, sometimes to the point where there is significant data loss.
You can post all the "tests" you want. You can believe me or not. Neither changes the underlying fact that running multiple instances of calibre of the same library will eventually destroy your library.
|
Also, sqlite is not a server. It's not
designed to be used in such a manner. If you want multiple users, use the content server.