-
Notifications
You must be signed in to change notification settings - Fork 838
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
ArgumentOutOfRangeException when combineing Model projection with Where-In in linq query #81
Comments
Confirmed as a problem. Fix has been submitted for review. Will get a new deployment asap. |
Should be deployed within the next few days. |
That is great news! |
fixed in 1.5.2 |
@ryancrawcour We have updated our nuget package to 1.5.2 and reran our tests. Our conclusion is that the provided unit test still fails erroneously. At this point i'm not sure what is going on. Did the fix not make it into the latest nuget package? Was the bug not understood and was something else fixed? |
Here's the unit test we built (derived from the code above) - https://gist.github.com/ryancrawcour/a833cd0f0543fcc9a8a4 This failed first which led us to finding the problem. Are you able to get the sql statement from the query? Or does it fail before it even gets here? |
I did try to catch a sql statement with Fiddler, but none came through. Apparently it fails before it gets there. This is the stacktrace I got returned:
|
per email conversation with @mmsommer this is now working. closing the issue as resolved. |
A where in, or Array.Contains(..) linq query results in an ArgumentOutOfRangeException when a projection (as in
Select(x => x.projection)
) is used before the where clause.I expected it to not fail and translate the expression into a where in query to Azure Documents.
Test code:
The text was updated successfully, but these errors were encountered: