-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Operand data type bit is invalid for max operator #472
Comments
Yes, we are using GROUP BY now to eliminate duplicate documents. I will add a similar unit test. |
Hi there. Is there any plans to support ordering boolean fields again? |
Can you give it a try and attempt to fix it? |
@sebastienros Sure. I've made a PR #503 to try to replicate the issue. Can you allow for tests to run? |
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting "Operand data type bit is invalid for max operator" error when using this on a query:
x.With<BooleanFieldIndex>(field => field.ContentField == nameof(BaseContentPart.Property)).OrderByDescending(x => x.Boolean)
Started working again after I commented it.
Is there any change in the past 2-3 months could cause this? I updated OC to the latest preview today.
The text was updated successfully, but these errors were encountered: