View Single Post
Old 10-10-2013, 01:37 AM   #4
silentguy
Connoisseur
silentguy doesn't littersilentguy doesn't littersilentguy doesn't litter
 
Posts: 88
Karma: 200
Join Date: Nov 2010
Location: Dortmund, Germany
Device: Kindle Paperwhite (10. Generation)
Was I being that confusing? Sorry. Okay, let's try this again.


My #read column is a tristate yes/no column and I use all three values. When you search in this column it works like this:

#read:yes finds books where it is set to yes
#read:no finds books where it is set to no
#read:false finds books where it is not set
#read:true find books where it is set, ie where it is yes or no

so far, so good, this is logical and follows the way the search works for any field.

Now for MY PROBLEM: when creating catalogs, there is a prefix option that does not follow this logic. There you have 4 predefined search values and they return the following :
#read:true finds books where it is set to yes
#read:false finds books where it is set to no or where it is not set
#read:undefined finds no books
#read:"" finds no books either.

Long story short, I think there is a small bug in the prefix search.
silentguy is offline   Reply With Quote