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.

Sign up for GitHub

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

Jump to bottom

Navigation fixup fails with composite FKs using server-generated values #6212

Closed
AndriySvyryd opened this issue Jul 31, 2016 · 0 comments
Closed

Navigation fixup fails with composite FKs using server-generated values #6212

AndriySvyryd opened this issue Jul 31, 2016 · 0 comments
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone
1.1.0

Comments

@AndriySvyryd
Copy link
Member

No description provided.

AndriySvyryd added a commit that referenced this issue Jul 31, 2016
@AndriySvyryd
Test for #6212
954c341
@AndriySvyryd AndriySvyryd mentioned this issue Jul 31, 2016
Merged
AndriySvyryd added a commit that referenced this issue Jul 31, 2016
@AndriySvyryd
Test for #6212
87aae36
@divega divega added this to the 1.1.0 milestone Aug 2, 2016
@divega divega added the type-bug label Aug 2, 2016
ajcvickers added a commit that referenced this issue Aug 11, 2016
@ajcvickers
Handle fixup of overlapping composite keys which get propagated store…
00c58d9 
… generated values

Issue #6212

This happens only in cases where the FK property is getting a store generated value by propagation, and this FK property is shared between two relationships, and if the metadata is built in a way that the propagation happens in a certain order. The fix is to to also use the pre-store generated value when looking up the new principal since this may not have been updated yet in the dependent map.

Also added more coverage for store-generated composite keys in general, and added some extension methods to make it easier to dump out a human-readable form of the model.

Also, see #6292, uncovered will testing.
@ajcvickers ajcvickers mentioned this issue Aug 11, 2016
Merged
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Aug 11, 2016
@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
@ajcvickers ajcvickers removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
3 participants
@divega @ajcvickers @AndriySvyryd