Bugzilla – Bug 8650
Separator for Multiple Items in Tags default behavior
Last modified: 2008-07-21 10:02:52 UTC
Currently, the "Music Library"."Separator for Multiple Items in Tags" setting defaults to off. If a common separator tag is discovered in 50% of the tags (possibly any tag, but particularly the genre tag) then the setting should default to on, using that tag. For instance, if 50% of the genre tags are found to contain a ; character, then the tag separator setting should be activated. Alternatively, a user message should be presented to the effect of "you seem to use a tag separator character; please ensure that it is set properly at http://server/settings/index.html" This is mainly an issue because of upgrade stability; if upgrading between revisions is being improved so that settings are retained, it's less of an issue.
I think the implementation of this would be very difficult. And the scanner is a separate process and isn't interactive, so there's no asking "Do do you want to _____?" half way through the scan. > This is mainly an issue because of upgrade stability; if upgrading > between revisions is being improved so that settings are retained, > it's less of an issue. I'm sure that this has always been the intention when upgrading. I can't imagine why this one setting would be lost and not the others. Are you sure you didn't delete your prefs in an attempt to do a 'clean' install?
> I'm sure that this has always been the intention when upgrading. I can't > imagine why this one setting would be lost and not the others. Are you sure > you didn't delete your prefs in an attempt to do a 'clean' install? That's a packaging decision -- the Debian packages do 'clean' installs, other Linuces may as well. Still, you've got a point that it's yet another problem with dependency on the Perfect Database. My root issue is that the Perfect Database still isn't here, and I've been using it and watching development since whatever Slimserver shipped with the first SliMP3. The migrations to SQLite and MySQL certainly fixed a lot, but the product still isn't very upgrade-safe, which will surely come up if I close this ticket and open another suggesting the Debian package should do upgrades instead of remove-and-installs.
(In reply to comment #2) > That's a packaging decision -- the Debian packages do 'clean' installs, other > Linuces may as well. Still, you've got a point that it's yet another problem > with dependency on the Perfect Database. I see. That's nasty. The database (currently) holds no server or player configuration information, only data for the libary. All you would have to do when upgrading is first copy the preferences (including plugin prefs) to another location and then copy them back after the installation. You'd still need to rescan the library, but you'd lose no settings.