TrackStat and long (>256) directory/file name

[schiegl]

Hi,

rating songs with really long directory/file names fails with:

2006-12-09 16:22:43.4322 TrackStat: Changing song rating to: 80
2006-12-09 16:22:43.4332 TrackStat::Storage: Ignore, url is 318 characters long which longer than the 255 characters which is supported
2006-12-09 16:22:43.4332 TrackStat: Calling TrackStat::Plugin
2006-12-09 16:22:43.4333 TrackStat: Entering setTrackStatRating
2006-12-09 16:22:43.4444 TrackStat: Exiting setTrackStatRating

As SlimServer itself has no problems managing these tracks, i'm interested if this limit could be raised.
The other ways would be to shorten the name. Usually I use "Artist - Album/Track - Title" to store files, in the classic domain this may give long names.

system:
SlimServer 6.5_svn
Trackstat 1.33

kind regards,
Markus

P.S. Yes i know, the tags will still contain the full names

[erland]

rating songs with really long directory/file names fails

The short story:
Performance in TrackStat gets really bad with filenames longer than 255 characters, so thats why the limit exists. On Windows it locks the whole computer, the power button is the only way out.

The long story:
TrackStat uses the filename as key column for its statistics, the reason is that the statistics needs to survive a slimserver rescan. The internal track identifiers used in slimserver is changed during rescan so I can't use them. The problem is that MySQL doesn't seem to be able to use indexes when querying database columns where the key column is defined as a datatype which are longer than 255 characters. MySQL starts to use 100% CPU in this situation, on Windows this locks the whole computer, the power button is the only way out. On linux it just makes the computer unusable which isn't much better.

So I can't change the limit unless MySQL is changed or slimserver decides to make a solution where the track identifiers used internally isn't changed when performing a rescan.

[schiegl]

okay, thx for explaining!

time for a new plan...