>I sure hope not. I applaud Andy for keeping it alive and an option for 7.6. Me too. MySQL has much better support tools available; I run various queries against the DB to find things that are miss-tagged, eg. tracks that haven't got replaygain, tracks that haven't got musicIP mixable status, etc. I haven't found any reasonable SQLite tools yet.
But it's irrelevant to me at the moment, in that I can't get either SQLite or MySQL to work in 7.6, so stuck with 7.5 for now anyway. >In my mind the jury is still out on which one will offer better >performance with large libraries. No doubt scanning will always be >much faster with SQLite Why do you say that? Most of the scanning time is reading files from disk and interpretting the tag content (or importing from MusicIP or iTunes) and then just writing rows to DB tables. I don't see any obvious reasons for SQLite being much faster. Both engines have to write to disk. MySQL was being held back in the SBS instance because it wasn't optimised. I run my own MySQL instance, which performs much better with alternative settings. Last time I had a semi-working scanner in 7.6, I think MySQL was actually scanning faster than SQLite. However, not a good comparison, because the libraries weren't visible to SBS, so I couldn't check that the scanned library was the same outcome. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
