Quote:
Originally Posted by theducks
You are ignoring my solution???
|
I don't think I am mate, but cryptic crossword puzzles aren't my cup of tea.
I've done what I wanted via an SQL Script. Read last_modified from last fridays metadata.db and wrote it to #mymodified in the current metadata.db.
Maybe a Bulk Metadata Edit RegExp could have done that - read one instance of a database and written to another - with a different schema - but I had neither the time or inclination to figure out how - considering the SQL tools & skills I have 'at my fingertips'.
So, I now have what I set out to do yesterday - a #mymodified TIMESTAMP column populated with the last_modified TIMESTAMP column as of last Friday. When I want to change a #mymodified value, I would normally also change the #bookstatus value; I already do that via metadata edit, so its no hardship to click the
Set 'My Modified' to today button, which btw also updates the time element
I am wondering if my 'problem' had something to do with the fact that I start calibre in View Managers Default configuration which up until half an hour ago had last_modified as its secondary sort field. I have the impression that not many of us use View Manager, and even fewer sort on a custom column (#bookstatus) and last_modified date (now changed to #mymodified).
For me at least this matter is resolved
BR