Quote:
Originally Posted by davidfor
The "Date" column is usually maintained by calibre. It is set to the current timestamp when a book is added to the library. While it is editable, my guess is that kiwidude didn't think it was a column that should be updated.
|
Quote:
Originally Posted by theducks
↑ ↑ ↑ ✔
{Date} has a purpose as David noted, and I belong to the school of 'leave the purpose intact'.
I know many others reuse columns for their own tasks, but we have the option to add our own and not mess with the data.
"When did I add this to Calibre? Oh! #$%, I reused the {Date} for last xyz"
Numbers, Dates, Logical (T/F) add a small bit of DB size, (unlike some of the others.) and take almost no performance hit (unlike calculated from other fields). So that should not be a major issue deterring making your own Date
and it avoids 2 different PI re-purposing (then later come here asking WHAT is messing with my last_read date.  |
Thanks for the feedback. It should be kept as it is and users should use custom date columns instead.