2019-08-02, 08:45
This looks very similar to a post from two years ago. Maybe the solution with the "strict mode" is also possible with MariaDB?
Also the reply to my github ticket on that matter suggested setting as watched again to resolve the issue.
I think the core of the problem is that the system time and/or timestamps of files is wrong. This should be fixed first.
Also the reply to my github ticket on that matter suggested setting as watched again to resolve the issue.
I think the core of the problem is that the system time and/or timestamps of files is wrong. This should be fixed first.
(2017-09-20, 14:22)raymondjpg Wrote: EDIT: I was able to resolve the issue, at least with a workaround, by disabling strict mode in MySQL. Apparently strict mode is now implemented by default in MySQL Server 5.7. Disabling strict mode involved removing STRICT_TRANS_TABLES from the line
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" in my.ini
(2017-10-08, 21:57)schapplm Wrote: I added this as an issue on github and will try to reproduce and fix this. I am not sure why the timestamp is invalid, though. It comes from the Kodi database MyVideos/files/lastPlayed which has text as data format in mySQL (and not timestamp, for some reason). The value '1970-01-01 11:00:00' looks valid. A workaround for now could be to set the lastPlayed entry to NULL.
