Quote:
Originally Posted by LadyKoori
Shouldn't the timestamp on the metadata in Calibre be newer then it was in CC? Basically my thought is, if the Read/Unread status in Calibre is newer, why is CC overriding it with the info it has?
I've got a work around so if this is just an issue I'm going to have to deal with I'm fine. I was just curious.
|
First, apologies for the delay. I looked at your post on my phone and then forgot to come back to it.
The timestamp plays no role in syncing the read column. Instead, it uses these rules in the order listed.
- If CC's read info differs from calibre's read info as of the last connect as a wireless device, update calibre with CC's info.
- If calibre's read info differs from what was sent to CC during the last connect, update CC with calibre's info.
- Change nothing
If both #1 and #2 are true, #1 wins.
Exactly what gets changed when during the sequence you describe isn't completely clear to me. My guess is that we are in the situation where you change Read on CC and FFDL changes Read in calibre between two connections. If so, then according to the rules CC wins.