Quote:
Originally Posted by davidfor
This was asked a long time ago. At the time, I suggested time zone issues. I don't remember if I looked at it then, or some other time for another plugin. If I remember rightly, it is calibre trying to compensate for a timestamp that in one place has a timezone and in another place doesn't, or doesn't need the timezone. |
This is interesting, because the link talks about this problem occurring in pubdate. In My testing, populating pupdate did not cause this problem. When I looked at the code to see why, I found that field_from_string was not used when populating pubdate, instead it calls parse_date (through a function called parse_pubdate).
So maybe someone fixed this for pubdate but did not do the same for custom date columns.