-
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: Projection with nested query fails with crashing SQL query #6824
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
This works in the current bits, we produce the following query plan:
|
'Current bits' is v1.2/2.0 ? As it still fails in 1.1.1 |
I mean our current dev branch (2.0) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Steps to reproduce
My designer allows the creation of models derived from entity models, containing derived elements. These Derived Elements are hierarchical DTO elements (or hierarchical document definitions for document databases) with (potentially) denormalized fields. These models are generated as POCOs and accompanying Linq projection methods to project a normal IQueryable to the desired derived element.
A query which should project a Northwind Customer - Order - Employee hierarchy to a hierarchy of DTO objects fails with a SQL query that has invalid fields. The root cause is likely the DefaultIfEmpty() that's been executed in memory, according to the log this is happening, however the Linq query doesn't contain any DefaultIfEmpty call.
The issue
Query run:
ProjectToCustomerOrder() is: (I'm giving the whole projection class so there are no hidden artificats)
The DTOs:
Full log with exception, query and stacktrace:
Further technical details
EF Core version: 1.0.1
Operating system: Windows 8.1
Visual Studio version: 2015
The text was updated successfully, but these errors were encountered: