Skip to content

Query: Key comparison should use object.Equals internally in query #21742

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
1 commit merged into from
Jul 22, 2020

Conversation

smitpatel
Copy link
Contributor

And associated changes to support translation.

Resolves #19407

And associated changes to support translation.

Resolves #19407
@smitpatel smitpatel requested review from ajcvickers and a team July 22, 2020 22:50
@ghost
Copy link

ghost commented Jul 22, 2020

Hello @smitpatel!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

This pull request was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Query: Key comparison for collection nav throws when PK is struct
2 participants