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
ToDictionary won't work, if using with navigation property #10312
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
Correct QM
Faulty QM
Seems like error in _Include optimization or |
This works in current bits, now using correlated collection optimizations rather than Include pipeline, which was source of the problem. Current QM:
|
maumar
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Feb 13, 2018
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
model from https://docs.microsoft.com/en-us/ef/core/get-started/full-dotnet/new-db
If I try to get #Dictionary and navigation property from query, I'll get an exception.
Exception message:
No coercion operator is defined between types 'Intro.Blog' and 'System.String'.
Stack trace:
Steps to reproduce
Workaround
change order of selected fields.
With query:
I can get what I want.
Further technical details
EF Core version: 2.0.1
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017 Enterprise
The text was updated successfully, but these errors were encountered: