mherger wrote: > If you're using a library.db with lots of tracks and lots of rescan > history (or whatever other odd coincidence I'm not aware of), you might > > reach the eight digit track ID issue.
Hi Michael, there is something that bugs me all the time:) In case of a clear and reimport scan the scanner gets the last ID and starts building the db from scratch but using one digit higher than the old "latest" ID. For this scenario (scan from scratch up) it would be nice(r) to get rid of the old stuff and start from scratch by using ID1 as first ID. (Same behavior for all IDs not only the Song_ID) I always stop the Server drop the tables and restart the server as workaround if i do a scan from scratch (for me that is a good workaround). Gruss Jan ------------------------------------------------------------------------ DJanGo's Profile: http://forums.slimdevices.com/member.php?userid=1516 View this thread: http://forums.slimdevices.com/showthread.php?t=104496 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
