[Supay]

Do I take it that simply changing 116 for 119 and KODI_18 for KODI_19 in the .sql files, with an appropriately named user and database in mariadb won't do the job?  I got a lot of SQL syntax errors in the output when i tried this, and so assume there have been too many changes between 116 and 119 for this to work?

Think I answered this myself as the syntax errors also state the version may be incorrect.  However it has highlighted another issue that may affect others.

After my attempts to bodge a multi user database failed, I decided to just go with multiple databases, one for each user.  I use Trakt to sync watched information as well anyway so can always go back to multi-user system later.  However, as I have used the format for the database name "Kodi_U01_Video_116" I decided to just stick with that for the Kodi v19 setup and in advancedsettings.xml added "Kodi_U01_Video_" as the name.  On rebooting Kodi, it started up fine and in mariadb I could see that a database had been created named "Kodi_U01_Video_119", exactly as expected, and showing the default tables within it.

On trying to scrape my NFS sources, it started running and seemed to read through the NFS share fine but then stopped with nothing showing up.  None of the movie items showed up in Kodi as identified.  I checked the Kodi logs and can see that it is reading the NFS share fine and recognising the individual folders and files.  However, the log had repeated errors regarding Kodi_U01_Video_119 as not existing.  I checked inside my mariadb container and could see the database existed there and the tables within it, and Kodi had only just created this anyway so it obviously had access to do this.  I confirmed permissions and the user had them, tried granting permissions across the board but still the same.  I deleted the database and tried this fresh a number of times, with the same results.

Now, the music NFS share worked perfectly.  That was just named james_music82 and scraped with no issue.  So I tried dropping the "Kodi_U01_Video_119" database again and instead setting advancedsettings.xml to use "james_video_" as the name instead.  In mariadb I saw it create "james_video_119" and on scraping my NFS share the content immediately started adding to the database with no errors this time.  I stopped it and dropped the database again, rebooted, and watched it create again and scrape fine again.  I dropped that database again, changed advancedsettings.xml to "u01_video_" and watched mariadb create "u01_video_119" and this scrape absolutely fine.  Dropped it and tried all over again, worked perfectly again.

I have very little knowledge of mysql/mariadb but something seems to have changed with Kodi v19 that makes it very unhappy with the format "Kodi_U01_Video_119" as a database name.  It can create the database but then seems unable to use it and so all scraping fails.  Hope this helps stop others banging their heads against it as the move to v19/119 goes ahead.