Posts: 44
Joined: Nov 2010
Reputation:
0
MeC!as
Junior Member
Posts: 44
2019-01-12, 10:02
(This post was last modified: 2019-01-12, 10:07 by MeC!as.)
Hi,
just wanted to ask if somebody else is facing this issue. I just updated to RC5 and the migration of the database (113>115 on a mariadb) worked fine. After the migration the spinning wheel in the database is spinning and spinning, but nothing happens. After restarting Kodi the screen stays black for a long view seconds and then Kodi starts but with an empty video database. I reverted back to RC4 and everything is back to normal again.
Posts: 20,070
Joined: Apr 2017
Reputation:
1,316
It is a known issue. Developers are looking for a fix at this very moment.
Posts: 16
Joined: Oct 2018
Reputation:
0
Phenomenon occurs on Windows 10, Android 7, Android TV 7 and Android TV 8, all using a shared remote database.
Kodi starts, but shows now media, and adding / re-scanning media or updating library is not starting either on any installation.
Posts: 16
Joined: Oct 2018
Reputation:
0
Oh, and the media-sources (from sources.xml) are present, but have lost their content-settings.
Posts: 44
Joined: Nov 2010
Reputation:
0
MeC!as
Junior Member
Posts: 44
It happened to me on mariadb 10.1.37
Posts: 14,213
Joined: Nov 2009
Reputation:
706
Klojum
Lost connection
Posts: 14,213
We're still trouble-shooting.
Posts: 505
Joined: May 2010
Reputation:
4
Damn, this happened to me too. I haven't done any investigation yet, anybody can comment on how I can roll back and/or how much I can recover?
Can I maybe go back to rc4 (if the old rc's are downloadable somewhere)
Thx
Posts: 102
Joined: Jan 2011
Reputation:
1
thica
Senior Member
Posts: 102
Looks like the new sql schema for views is using function which are supported by more recent sql server versions
SQL Error (1349): View's SELECT contains a subquery in the FROM clause
Subqueries are not supported in older MySql / MariaDb versions
___________________________________
No Backup, No Mercy
Posts: 30
Joined: Mar 2009
Reputation:
1
RedsGT
Junior Member
Posts: 30
I was running MySQL 5.5.x. Upgraded 5.5.x->5.6.x->5.7.x and all is well now.
Posts: 18
Joined: Jul 2015
Reputation:
0
Is there any idea of ETA for the fix being pushed out?