Since you’ve already applied the “mediumtext” workaround to c08, that leaves c20 as a possible culprit, since it’s also a very long string (around 46k characters). While 46k is smaller than the maximum size for a text column, which is 64k, I think it’ll depend upon which character set is being used. (For example a UTF-8 character is often two bytes long – and can be up to four bytes in more esoteric cases.)
I’m running Maria 10.4 on a Win 10 PC and testing on a Vero 4K. I set my Avenengers Endgame folder scraping settings to exactly how you posted. I refreshed from the internet and got the same error message in my logs and a failed scrape. I then edited c08 and c20 to mediumtext and tried it again and was able to scrape successfully. I think this probably lends further support to my earlier statements about the db version.
On a related note I question the need to basically check every box in the scraper settings. This makes for a very large increase in the amount of data being stored in the db.
This is now about getting the MariaDB working, so if you want me to post a new thread, let me know. Otherwise…
I set up a new, empty DB using MariaDB on my headless Ubuntu server. I verified remote access is working via DBeaver and can browse the default databases there. I changed one of my Kodi instances (the NUC running Window 10) to point to the Ubuntu server in advancedsettings.xml. I then refreshed one movie folder in my library by changing the content type back and forth, so it would ask about updating the contents. That finished, but I don’t see the myvideos116 database on the Ubuntu server, so I don’t believe it’s actually using the central DB and is instead using local info.
Any idea where I should could start my troubleshooting? The Kodi log doesn’t seem to be giving me any hints, but I may not know what I should be looking for.
Since you guys are helping me out and to be fair, I instead set up the Vero to access the new DB. After pointing the Vero to the new DB, I rebooted the Vero, and I needed to set the content type on the sources again. As soon as it started scanning, the DB was created and getting populated. I’m not sure why the other Kodi device didn’t do so, but I’m not too concerned about that at the moment.
I’m going to let the DB get fully populated and then see what the status of the problematic movies are. I haven’t yet changed any of the columns to mediumtext yet, as I want to take this one step at a time.
Thanks for all the help so far. I’ll return with more updates as this progresses.
EDIT: I realized I didn’t answer your question. Yes, did.
And old versions of the DBs don’t handle mixed charsets very well. (sizing by “bytes” instead of “characters” for example, which is often the cause of oversized DB saves… (client app sends 40 characters, which it knows is less than 64 chars… but the DB then see it as 80 bytes and vomits… nowdays DB’s pretty much always assume UTF-8 instead of ASCII like in the old days) Upgrading the DB is probably the easiest solution. Usually, you can just upgrade in place and it will convert your schemes for you. (including mysql->mariadb if I recall correctly)