View Single Post
Old 04-21-2011, 07:34 AM   #6
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,864
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Nexus 7
Quote:
Originally Posted by kiwidude View Post
@dwanthny - you misunderstand me I think. They would have their own Calibre library that is not in dropbox - the metadata.db is not shared. As I said above they just use Dropbox to Add from as a source folder into their local library. No concurrency issues whatsoever.
I understood you. Do you use Dropbox? If they all decided to copy to their dropbox (local machine) at or close to the same time then it is probable that they will cause the metadata.db file in the dropbox to get conflicted and not update the cloud or another's local copy of the dropbox metadata.db file.

Update: its not a calibre concurrency issue it is a dropbox concurrency issue.

Last edited by DoctorOhh; 04-21-2011 at 07:36 AM.
DoctorOhh is offline   Reply With Quote