Kodi Community Forum
v18 Recently Added not working - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: v18 Recently Added not working (/showthread.php?tid=359241)



Recently Added not working - stramoski - 2020-12-20

I'm using mysql for my library to sync between several machines (android on my phone, FireTV sticks, and windows pcs) and they are all experiencing the same issue.

When I select "Recently Added", whether on the TV or Movies section, kodi navigates to the "root" of that section instead. I.e., I select recently added in the movies section and am just directed to the menu with "Recently Added", "Genres", "Titles", etc.

I've turned on logging, but I am not sure what to do.

I tried recreating my entire MySQL library, but the problem just came right back.

https://paste.kodi.tv/raw/hiyedanede


RE: Recently Added not working - Klojum - 2020-12-20

2020-12-19 14:55:47.671 T:6740 NOTICE: Disabled debug logging due to GUI setting. Level 0.
Always restart Kodi when enabling debugging, so more details will be shown from the start.

2020-12-19 14:55:52.304 T:6740 NOTICE: MYSQL: Connected to version 8.0.22-0ubuntu0.20.10.2
..
2020-12-19 14:55:54.642 T:6396 ERROR: SQL: Missing result set!
2020-12-19 14:55:58.284 T:6740 ERROR: CVideoDatabase::GetMoviesByWhere failed
2020-12-19 14:55:58.541 T:4144 ERROR: CVideoDatabase::GetTvShowsByWhere failed

MySQL 8.0 can have its nags, and apparently retrieving the 'Recently added' listings is a problem.

Can you enable the Database component in the debugging section, restart Kodi, reproduce the error(s), and provide a new debug log file?


RE: Recently Added not working - DaveBlake - 2020-12-20

Solution to ERROR: SQL: Missing result set! and MySQL 8.0 given here https://forum.kodi.tv/showthread.php?tid=357217

Cause of the error is in MySQL solved by changing the sort_buffer_size setting