[Solved] All book dates the same date after update to 6.6.1

[ownedbycats]

Originally Posted by Quoth

Editing a tag case (and some other columns) on one book will put "now" as the date not just on that book but every book that uses that "global" data . It's because the tag is only stored once and a case change isn't regarded as a new tag/data.

no, not the date column. Perhaps last modified. It probably happened because the original poster accidentally misclicked on the date field and activated it.

[theducks]

Originally Posted by Quoth

Editing a tag case (and some other columns) on one book will put "now" as the date not just on that book but every book that uses that "global" data . It's because the tag is only stored once and a case change isn't regarded as a new tag/data.

I think the OP somehow changed {date} (usually the date the record was created), not {last_modified}

[CaptainTivo]

Originally Posted by Quoth

Editing a tag case (and some other columns) on one book will put "now" as the date not just on that book but every book that uses that "global" data . It's because the tag is only stored once and a case change isn't regarded as a new tag/data.

I don't understand. If I, say, select ALL books and then click "Edit Metadata" and then in the Remove tags box, select some tag and click Apply, it will change the "date" field of all the books selected? This makes no sense. I can see where it would change the "modified" field but I thought the "Date" field was the system date of the actual file imported?

I did a google search and found this. But it is dated 2011 so the behaviour may have changed since then.

"As far as I know the date column is never changed. Saving to disk and then adding preserves dates, that is by design. If you dont want that behavior turn off creation of OPF files when saving to disk."
-Kovid Goyal

[ownedbycats]

Originally Posted by CaptainTivo

I don't understand. If I, say, select ALL books and then click "Edit Metadata" and then in the Remove tags box, select some tag and click Apply, it will change the "date" field of all the books selected? This makes no sense. I can see where it would change the "modified" field but I thought the "Date" field was the system date of the actual file imported?

I did a google search and found this. But it is dated 2011 so the behaviour may have changed since then.

"As far as I know the date column is never changed. Saving to disk and then adding preserves dates, that is by design. If you dont want that behavior turn off creation of OPF files when saving to disk."
-Kovid Goyal

No, it won't change unless the user changes it (even by accident). It will edit the last_modified column, but I don't think that's user-editable anyways.

[Quoth]

Originally Posted by ownedbycats

no, not the date column. Perhaps last modified. It probably happened because the original poster accidentally misclicked on the date field and activated it.

I meant last modified. The date column is usually when the record was created?

Sorry.

[ownedbycats]

Originally Posted by Quoth

The date column is usually when the record was created?

Yes, unless changed. I sometimes change it to the original filedate (imported to a custom column with with GetFileName) when adding older files to my library.