Quote:
Originally Posted by Divingduck
Hi chaley,
I setup a new Windows 10/64bit system with only calibre 64bit installed. I got the same error behavior. 
Pls see attached pic. |
I found the problem. I created a totally clean calibre configuration and the errors started appearing. The problem is that some of your virtual library search expressions use "naked" searches; searches with no column prefix. Example: Bücher Deutsch has the expression
Code:
languages:"=Deutsch" or "=German"
Because the second term, "=German", has no prefix, calibre will search in every calibre column, including the composite column computing the virtual libraries. Because that column hasn't yet been computed, the searches for the virtual libraries are evaluated again. This causes recursion because the search will hit the composite column and start over again.
There are several cases in your VL definitions where you have a naked term. If I remember correctly they are all of the form col:value1 or value2. I am sure that you meant col:value1 or col:value2.
The reason I didn't see the error at first is that I have checked the box in Preferences / Searching that limits the fields searched by naked terms.