View Single Post
Old 08-01-2018, 01:20 PM   #4
itimpi
Wizard
itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.itimpi ought to be getting tired of karma fortunes by now.
 
Posts: 4,553
Karma: 950151
Join Date: Nov 2008
Device: Sony PRS-950, iphone/ipad (Marvin/iBooks/QuickReader)
Quote:
Originally Posted by AntonGolubev View Post
Hi Kovid,

Thank you for replying and the link! I see the point, but I possible the things can be improved with little effort.

Is it possible to force running Calibre to re-load the database from the filesystem, forgetting his state? E.g. if I forgot to close it on one PC, to make it not overwrite the changes, which another instance already introduces to the disk?

Kind regards,
Anton Golubev
i think you will find that the problem is on the syncing software in that it does not do the sync until Calibre is shutdown and closes the database! This means that if you start another Calibre instance on a different machine it does not know about the changes made on the still running instance so the two instances end up trampling on each other’s changes.
itimpi is offline   Reply With Quote