Skip to content
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

Initial change tracking for skip navigations #21516

Merged
merged 5 commits into from
Jul 10, 2020
Merged

Conversation

ajcvickers
Copy link
Member

Part of #19003

Covers only the simple case of collection skips with non-composite, non-alternate keys and simple concrete join table containing only two FK properties.

Many-to-many tracking queries are enabled, but some are skipped due to query translation errors.

@ajcvickers ajcvickers requested a review from a team July 4, 2020 21:00
Copy link
Member

@smitpatel smitpatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed the translation error arising in #21517 (tested by putting fix on this branch)

test/Directory.Build.props Outdated Show resolved Hide resolved
@ajcvickers ajcvickers requested a review from smitpatel July 5, 2020 18:22
{
var associationEntry = FindAssociationEntry(entry, otherEntry, skipNavigation);

if (associationEntry == null)
Copy link
Member

@AndriySvyryd AndriySvyryd Jul 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we agreed to limit this to entity types that only have the foreign keys

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I 100% agreed. ;-) Anyway, I'm going to look into this more, so the code here is not final.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description says:

Covers only the simple case of collection skips with non-composite, non-alternate keys and simple concrete join table containing only two FK properties

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I talked to your manager, and he said it's okay to merge this now and revisit later.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps I should speak to your manager then 🙃

@ajcvickers ajcvickers requested a review from lajones July 6, 2020 19:00
Copy link
Contributor

@lajones lajones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would definitely get @smitpatel to look over the query changes. But for my part it looks good.

@ajcvickers
Copy link
Member Author

@smitpatel Any more comments on this?

Copy link
Member

@smitpatel smitpatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine to merge. @AndriySvyryd should also take a look when he returns in case I missed anything.

Part of #19003

Covers only the simple case of collection skips with non-composite, non-alternate keys and simple concrete join table containing only two FK properties.

Many-to-many tracking queries are enabled, but some are skipped due to query translation errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants