-
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
Query: SubQuery with Aggregates causes unneeded queries in 1.0.0 and throws exception in 1.1.0-preview2-22683 #6982
Comments
Forgot to attach the project. Here it is. |
cc @maumar in case this is already fixed in 1.2. |
This exception was fixed in 1.2.0 but the scenario hit a bug later in the pipeline. Here is the simplified standalone repro:
|
New exception is: The query plan is as follows:
|
The exception is fixed in the current bits, N+1 queries are generated for this scenario due to #8083 |
Attached is a project that exhibits the behavior.
In EF Core 1.0.0 extra queries are generated and "warn" messages are logged. These extra queries are unneeded as the primary query generated properly retrieves the data that is needed. In fact, the queries are duplicated over and over again. Attached is the output.
EF1_0_0_output.txt
In EF Core 1.1.0-preview2-22683 the same code causes an exception and no querying is performed.
The text was updated successfully, but these errors were encountered: