Phil Meyer;206437 Wrote: > I'm having trouble with the Custom Scan - MixedTag scanning module. > I've rescanned the library okay, but when I do a MixedTag scan, I get a > few occurances of the following: > > 2007-06-03 01:31:27.8906 CustomScan: Failed to scan SlimServer tags: > DBD::mysql::st execute failed: Data too long for column 'url' at row > 2875 at > P:\Music\SlimServer\trunk\server/Plugins/CustomScan/Modules/MixedTag.pm > line 269. > > I tried turning on customscan debug messages, but don't see anything > else useful in the log.
That's actually probably a character set problem. It's confusing - older versions of MySQL show that error message when data is truncated as it's inserted into a column. This happens when a character is encountered that isn't unicode. I believe newer versions have changed the error message. http://bugs.mysql.com/bug.php?id=18908 SlimServer seems to work around these character set issues by using binary columns for things like URLs and track titles. I've found that with my library this isn't necessary except (for some reason) for cover art paths. It may be necessary for the Custom Scan plugin to ensure that all data is utf8 encoded before trying to put it in the database. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=35815 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
