Originally Posted by chaley
I was reluctant to make the change to allow search/replace to update date fields precisely because of the possibility of this sort of problem. Calibre was not designed to auto-convert between types and apparently the database calibre uses (SQLite) permits writing trash values into date fields. Sigh ...
The next release (0.8.64) will attempt to convert the string to a date in this case and some other cases that I found.
Thanks! It looks like the unicode date string to ISO date value conversion doesn't work either... so that'd be nice.
How come the import conversion works correctly? Could the same code be used for the search/replace?