Quote:
Originally Posted by bodiccea
@BetterRed,
I want the file system modification date to be the MAX({last_modified}, {timestamp}).
Or, to be more clear: I must set my 3000 books modification date on file system automatically from calibre data.
So any GUI (finder or other) is not useable: I have to extract the dates from calibre automatically, and only a script (already done, look in a previous message) can do it.
So the date seen on web site will almost be correct.
I did read somewhere that some changes on boot itself (for instance adding a chapter, this kind of things) may change the {timestamp} field, so taking the MAX wil be the secure way.
If this {timestamp} ("date" column in GUI) always stays the same, and is the insertion book date in library, the MAX() will maybe not be necessary). This field is not really well documented.
br.
|
{last_modified} has no clue of what the actual book files Modified date is.
It refers SOLELY to DB actions. It will record the time you ADD (a book)
eg. using Open_with to Edit the EPUB does not change the {last_modified} value. (
I keep a custom column for the last edited date which is manually set) changing that, also bumps the last_modified timestamp
So if you are more interested in EDITED Dates, create your own column.
