'Sometimes' timestamp column has incorrect data

[_dan_]

I added 3 books via Drag and Drop to calibre at the same time, two books got the correct timestamp in the books table, one book got '0101-01-01 00:00:00+00:00' instead which results in problems with connected apps.
last_modifed displays the correct date though.
I am using calibre 7.12 on macOS.

[Kovid Goyal (kovid)]

Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.

[_dan_ (dan-void)]

Still happening.
Added a new book, table books, timestamp -> 0101-01-01 00:00:00+00:00
Calibre 7.13 macOS

[Kovid Goyal (kovid)]

Does not replicate for me. Adding a new book either sets the date to the current time or the value of the timestamp metadata in the book.

[_dan_ (dan-void)]

I can reproduce it with a new library.
When I first add the book, the timestamp is current time but after downloading (manually) metadata (Goodreads, with Goodreads ID) timestamp is then 0101-01-01 00:00:00+00:00

[_dan_ (dan-void)]

Adding a different book, clearing metadata and putting 'Goodreads:60929' in the ID field then pressing download metadata ends in the incorrent timestamp as well.

[Kovid Goyal (kovid)]

So then report the issue to the author of whatever metadata plugin is giving you that date. None of the builtin plugins do that.

[_dan_ (dan-void)]

Did not realise the plugin was the culprit. Thank you!