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

Fixup can be inconsistent for 1:1 relationships changed in store #6171

Closed
ajcvickers opened this issue Jul 26, 2016 · 0 comments
Closed

Fixup can be inconsistent for 1:1 relationships changed in store #6171

ajcvickers opened this issue Jul 26, 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

@ajcvickers
Copy link
Contributor

If an FK value for a 1:1 relationship is moved from one row (entity) in the database to another row (entity) in the database while the first is loaded, then if the second is later loaded fixup can be inconsistent because both entities will have navigation properties pointing to the single principal.
ajcvickers added a commit that referenced this issue Jul 26, 2016
@ajcvickers
Make fixup consistent for 1:1 relationships changed in store
6baf3b0 
Issue #6171

The fix is to to make sure that any existing dependent that points to the same principal has its FK and nav props nulled out.
@ajcvickers ajcvickers mentioned this issue Jul 26, 2016
Merged
@ajcvickers ajcvickers self-assigned this Jul 26, 2016
@ajcvickers ajcvickers added this to the 1.1.0 milestone Jul 26, 2016
ajcvickers added a commit that referenced this issue Aug 8, 2016
@ajcvickers
Make fixup consistent for 1:1 relationships changed in store
333db0e 
Issue #6171

The fix is to to make sure that any existing dependent that points to the same principal has its FK and nav props nulled out.
@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 8, 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
1 participant
@ajcvickers