View Single Post
Old 07-09-2021, 05:39 PM   #2
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,489
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
This isn't really a recursion problem. Recursion means that X uses X, for example when the column evaluator must use the column evaluator to get a value.

What you describe is a case where the logical expression includes "A and not A", which as written is a contradiction. Your searches aren't so clear because the left-hand side includes other conditions not related to A, but it still could end up in the same place.

The answer: don't do that. You have found one way -- construct a search that doesn't use the same subsearch more than once. Another way that might work is to use restrictions, available in the virtual library tab, because they are fully evaluated before sub-searches are done.
chaley is offline   Reply With Quote