Interesting. It makes some sense to store the DB with the music files, though at the expense of adding some complications.
Versioning of the library DB vs the installed SQL engine will need to be managed. This could hit on server software upgrade or when moving storage from one Touch (or other TinySC device) to another. Easy enough to check for this on connection. Device hot disconnect, as mentioned before, could be an issue. I suppose some consistency checks could be run on the file system and library DB, perhaps triggering repair attempts when errors were found. It also brings into question the longstanding built-in assumption that there will be only one library per SC installation. The library is essentially defined as a database instance. And rather than one central DB, we'll now have many distributed DBs. I suspect that switching between the contents of DBs/libraries will quickly become desirable. Blending libraries may also be desirable, though that would be a harder problem to solve. There have been longstanding requests for the ability to segregate and manage multiple libraries on a single SC installation. I had assumed this might be implemented as multiple logical libraries within one DB. Now we are looking at managing multiple physical libraries/DBs. If switching (or blending) physical libraries is implemented it seems like that could be leveraged to cover the multi-library feature request. Each library could be stored in its own DB, available via the library switching/blending feature. -- fuzzyT ------------------------------------------------------------------------ fuzzyT's Profile: http://forums.slimdevices.com/member.php?userid=13 View this thread: http://forums.slimdevices.com/showthread.php?t=67523 _______________________________________________ Touch mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/touch
