-
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: Identify defining query projection as entity type #17158
Comments
This would allow us to apply Include on top of defining query or use defining query for keyed entity type where tracking is needed. |
Some notes on the conversations I had with @smitpatel about this, in case they are useful in the future: My understanding of this issue is that projecting an object with a Note that these are the same effects of projecting an object using Currently this will affect any key-less entity that references other key-less or keyed entities. If we re-enable defining query support for entity types (see #13358) this will affect keyed entity at the root as well. We discussed a couple of options to address both the current and future incorrect behavior:
|
From an earlier discussion, I believe 2 is the best option (if we agree on above definition of mapping). |
As per #18903 we want to replace current defining query with provider specific versions which avoids this issue altogether. We don't need to identify projection as entity type. In either provider it would be taken as a data mapping for the entity type rather than making the LINQ part of query expression. |
We treat
new T { }
as non-entity projection which we don't track and treat as entity shaper. Since defining query apply projection that way, we need to process it accordingly for include/shaper.The text was updated successfully, but these errors were encountered: