-
-
Notifications
You must be signed in to change notification settings - Fork 326
boolean queries can give wrong results #2371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
And for the record, removing those filterQuery calls (just using q for both) fixes the above case, but breaks others, like this one:
|
The query is split into two "equivalent" queries which can be applied in stages, before and after valuation:
which I believe was done to accommodate #1625 (2021), making cur: and amt: match the pre-valuation amounts. But this is incompatible with boolean queries (#1989, 2023), which can't be split this way without changing their meaning. |
Posted a draft fix, #2373, with some ideas. |
Fixed by #2387. |
Uh oh!
There was an error while loading. Please reload this page.
I found an example that's easy to reproduce:
This should not be showing the negative checking postings. I expected to see:
The problem is with the filterQuery calls in journalValueAndFilterPostingsWith. It doesn't know how to handle a non-trivial boolean query, and ends up altering it:
The text was updated successfully, but these errors were encountered: