there is something that bugs me all the time:)
And you don't even bother to tell us why. It can't be the numbers themselves which are bugging you?
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.
That's correct.
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)
You shouldn't care about the track ID at all. Because it can be different after every scan. Even if that's not the case, then it's just by chance. But the ID is just a unique number assigned to every record. Always try not to give the primary key any special meaning. I've regretted using some existing value as the pk several times before...
If you need something persistent, try the url hash. -- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
