MrC Wrote: > I was wondering if slim's database was versioned, and if that version > was increased when changes are made to the schema? Yes, it is versioned. There's a table named 'metainformation' that contains a 'version' column. Currently it's at version 15 for rev 4303 in the 6.2 trunk.
> 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. If you're doing a 'clear library', this should be unnecessary. A 'clear library' handles pretty much any problem I've seen, although completely deleting the database might sometimes necessary for severe corruption. One thing I wish somebody would do, though... update the Rescan Music Library scheduler plugin so that it would give the same options as the built-in interactive rescan. Then you'd have the option of doing a 'clear library' when you do your nightly scheduled rescan. > 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? I think it already does this - whenever the schema changes and the version is updated, SlimServer does a rescan upon startup (actually, this is kind of a PITA if you keep up with the nightlies or SVN updates, since the server is pretty much unusable until it completes the rescan). -- JJZolx Jim _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
