I was wondering if slim's database was versioned, and if that version
was increased when changes are made to the schema?

I've noticed after installing various nightlies, even after doing a
full rescan, bogus artist, album, track, etc. information is presented.
I just ditch the Cache folder and rebuild, but perhaps a more
automated, reliable mechanism would result in fewer problems and
support requests.

Would it be possible for slim upon start to examine the on-disk
database version, compare it with its concept of what the current
database should be (similar to linux's symbols for loadable modules),
and delete/rebuild a new one if the versions were inconsistent?


-- 
MrC
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta

Reply via email to