-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
SkipWhile: Processing of the LINQ expression failed #18962
Comments
Putting this on the backlog to throw a better exception. |
Probably the exception is already improved. |
current exception:
|
@maumar But that exception message still doesn't tell me why it couldn't be translated. It's basically the same as the original exception message with the query inside it. But I feel the the exception should say that |
The exception message in EF Core 2.2 is still much better because it tells me that it's the |
When query translation fails, if there is anything specific we indicate the reason (like using not mapped property). Otherwise it is the last query operator in exception message which fails the whole query. We will consider improving it in future if there is enough user feedback that it is not clear. |
Steps to reproduce
After running this, I get this exception:
I assume this is because
SkipWhile
isn't actually implemented (looking at #14104), but the error message is really cryptic. It's anInvalidOperationException
simply saying that processing the expression failed and mentions that it might be a bug in EF Core.Running the same code under EF Core 2.2, I get:
which is much clearer - it tells me that
SkipWhile
isn't supported. This is at the very least a regression in the readability of this error message.Further technical details
EF Core version: 3.0.0
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET Core 3.0
Operating system: Windows 10 Version 1903
IDE: Visual Studio 16.4.0 Preview 5.0
The text was updated successfully, but these errors were encountered: