Post Reply 
MinimServer Conflicting Values in Filter Warning
03-09-2017, 20:52
Post: #3
RE: MinimServer Conflicting Values in Filter Warning
The short answer is that you need to change EncodingTime.yearMonth.index to EncodingTime.yearMonth.index.sort. To understand why, read on....

Suppose your library contains albums tagged with a mixture of the following:

COMPOSER=Johann Sebastian Bach
COMPOSER=Bach, J.S

You decide that you want to see all these in your composer index as J.S. Bach, so you configure MinimServer to set all the index values to J.S. Bach. Because this doesn't change the sort values, you would get index entries for J.S. Bach in both the B and J sections of the Composer index. The J.S. Bach entry in the B section would contain everything tagged COMPOSER=Bach, J.S and the J.S. Bach entry in the J section would contain contain everything tagged COMPOSER=Johann Sebastian Bach.

This doesn't seem like a good idea, so MinimServer doesn't allow multiple tag values with the same index value and different sort values.

In your case, the sort values are so close together ('2009-09-16 10:36:30' and '2009-09-16 10:34:16') that this problem is unlikely to arise. However, the sort values are different, so MinimServer produces a warning to tell you about it.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: MinimServer Conflicting Values in Filter Warning - simoncn - 03-09-2017 20:52

Forum Jump:


User(s) browsing this thread: 1 Guest(s)