>I suppose the MySQL process was using a lot of CPU during this time ? >Could indicate that something needs to be optimized. > I think so - can't remember. It displayed the hourglass mouse pointer in the Web page. I got the impression it wasn't doing anything though - couldn't see any disk activity, etc. I assumed because of the errors, which affected table joins, the job had either cancelled or was stuck doing the wrong stuff.
Last night I did drop the database and recreate, and the table/column collations now seem to match. Delete unused statistic is now running again without reporting errors - thanks. >Just remember that if you do this you might loose >information that will take some time to re-create. As an example if you >use the "LastFM" or "Amazon" scanning modules in the Custom Scan plugin, >you will need to perform a rescan with these which will take some time. > Not too bothered - I'll run one rescan each night until I'm back to normal. >However, a clean start is really the best solution if you like to avoid >future problems. At the moment you have a database that looks different >than the database of most SqueezeCenter 7.2 users. Your database will >might be different even if you run the convert SQL directives I >mentioned above, those directives only make sure the collate matches >but doesn't make sure they are the same as a clean installation. > Yes, I had tried to change some table/column collations and I still couldn't get it to work, but recreating the DB seems to have fixed my errors. >By the way, I just checked the code and if you want the history in >track_history to match your new path's, you will have to apply the same >change as in saveTrack also to the corresponding section in the >addToHistory function in Storage.pm > I suspected that - I started to edit that function yesterday, but wasn't sure what it was for, so I reverted the change. I'll reapply it. I don't think I use track_history for much - doesn't the track_statistics/tracks_persistent hold last played and count columns, and trackstat queries look at that data? Are there many places that use track_history? Phil _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
