Gaaaah, can't believe they'r planning to change the DB numbers for the final 19 release after running with the same DB version as Kodi 18 all this time with the alphas/nightlies
. (At one point it was mentioned there may be some support to avoid this very issue with each new Kodi version but it looks like that all went down the crapper.)
My knowledge of MySQL (MariaDB 10) literally ended at the ultimately unnecessary & extensive research I did to get it all initially set up & running. It's all worked absolutely perfectly since just with the MySQL server itself running on one of my NAS, (no additional Trakt add-ons etc. etc.)
Migrating/exporting the DB from one version to another, however. In a word,
YIKES!!!!!
I don't want tens of thousands of bloody .nfo files everywhere in with all of my media & I don't presently have any .nfo files in use with my DB at all. It's incredibly lean & clean as it us, & I'd prefer it stayed that way.
I just want to migrate it all as is with PHPMyAdmin so it seamlessly jumps from one Kodi version to the next. So far, however, I can't find anything to explain the whole process in simple terms for the complete MySQL dummies like me
!!
It's been an awesome option to have, especially as we're constantly jumping between or testing all of the various MINIX devices which would have been a nightmare maintaining a separate library on each individual device, but Christ I hope I don't have to end up rebuilding a new MySQL library from scratch just for Kodi 19. (Not that, that is a slow process, it actually only takes a few minutes & it's all done ready to go.) It's the
countless hours it would take for me to manually note all of my watched status & user ratings for all of my media which could potentially take days
. (Not really bothered about resume points if starting a whole new library & there wouldn't be that many to bother about that anyway.). But, I have countless files with watched status/user ratings that I'd really want to preserve after all of the initial effort & growing the MySQL library since starting it all up.
With a library as large as mine, this could potentially become a serious headache for something that's actually supposed to make the whole concept easier