I'm not sure if this warrants a full Bug Report, so I'd like to discuss what I've found.
(Similar to this thread)
During a recent update to my library, I came across a movie that just would not scan (for posterity's sake, Star Wars: The Force Awakens). I tried multiple Add-Ons (and different settings for each). No dice.
After digging through the logs, I discovered the issue seemed to be caused by a value that had exceeded its intended column's limitations (myvideos107 -> movies -> c08).
The default "TEXT" Data Type limited the input to 65,535 (if
this source is correct) characters, well under the size of the string (83,142 characters). Changing the Data Type to "MEDIUMTEXT" allowed the movie to be added as expected:
ALTER TABLE `myvideos107`.`movie` CHANGE COLUMN `c08` `c08` MEDIUMTEXT NULL DEFAULT NULL;
I would have to really dig through my library to try and find another instance of this issue, but I don't know whether this qualifies as a bug. Certainly something in the minority, but worth mentioning nonetheless.
Due to the popularity of the movie, I believe there are an unusually large number of available art files. Should this be reported to the Add-On maker so that they can limit the string length? I just don't know. Both
Universal Movie Scraper and
The Movie Database Add-Ons failed to add the movie. Also, I can see where some people would prefer to have the options to choose from...
Thoughts? Will an update to Kodi copy over the new Data Type, or would I have a huge problem on my hands when v18 is ready for mass adoption?
ASSOCIATED LOG ENTRIES