2013-08-12, 06:51
Yes, normally the lastplayed date is blank ("") until it is played... Strange that it has newer dates, but that would explain why the script ignored the older lastplayed dates present in the DAT file.
If you want to restore all of the values from the DAT file, even those that may be older than values now in the database, then set "@watched.overwrite=yes" on the command line when you restore the file again - this should set the lastplayed dates to be whatever is in the file.
The reason I implemented it like this is that you might backup your watched statuses, then watch (or resume) one or more movies, then for whatever reason later still you decide to restore the status file (maybe you removed and re-added a movie) but you don't want to lose those watch status updates that occurred after the last backup.
I'm interested in those items that didn't restore at all though, I'd like to understand why they didn't match.
If you want to restore all of the values from the DAT file, even those that may be older than values now in the database, then set "@watched.overwrite=yes" on the command line when you restore the file again - this should set the lastplayed dates to be whatever is in the file.
The reason I implemented it like this is that you might backup your watched statuses, then watch (or resume) one or more movies, then for whatever reason later still you decide to restore the status file (maybe you removed and re-added a movie) but you don't want to lose those watch status updates that occurred after the last backup.
I'm interested in those items that didn't restore at all though, I'd like to understand why they didn't match.