Quote:
Originally Posted by davidfor
Adding validation that the date coming from GR is not null so that it doesn't clear the last read date in calibre is reasonable, and I'll look at it. But, if you still have a book doing this, can you run calibre in debug mode, sync and post the log. I don't think there is enough debug logging happening to show me exactly what is wrong. I'm wondering if the date is coming down but it isn't being converted properly.
|
I've performed the workaround I described on all the books that were affected, but if/when I get another, I'll post the log.
Quote:
As to not syncing the date if it is already filled in calibre, I disagree. The "Date read column" in the configuration is for the last date read. Syncing from GR brings the last read date it knows about. Whatever the value is that comes from GR should replace the value in the calibre library. That is what the function is designed to do, so anything else would be a bug or a change in function.
If what you are actually recording is "Date First read", then you should either not be syncing the date read, or use a separate column in calibre.
|
Yes, I can see that. I'm not sure how I'd populate the "date first read" though, unless I was sync'ing *that* from GR, in which case it would still be over-written by a later date-read. Adding it manually would seem to be the only alternative. Am open to suggestions.