| 2020-06-14 14:50:05 |
Marc Grissom |
bug |
|
|
added bug |
| 2020-06-14 14:53:02 |
Marc Grissom |
description |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp of Date field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp or Date field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
|
| 2020-06-14 14:53:29 |
Marc Grissom |
description |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp or Date field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp (aka Date) field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
|
| 2020-06-14 14:54:08 |
Marc Grissom |
description |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp (aka Date) field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
Windows Calibre portable version 4.18
I was testing out changing metadata via the CLI and noticed this weird behavior. The command below is supposed to set the timestamp (aka Date) field to February 1, 2020. However it ends up getting set to February 2nd. If I try the 29th, it will get set to the 28th. Dates in between seem to always get set correctly. It seems to do this with all the other months as well.
"D:\Software\Calibre Portable\Calibre\calibredb.exe" set_metadata --library-path "D:\Software\Calibre Portable\Calibre Library" --field timestamp:2020-02-01T22:00:00+00:00 1 |
|
| 2020-06-14 16:51:18 |
Kovid Goyal |
calibre: status |
New |
Fix Released |
|
