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

Original values must be required for principal keys #6106

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

Original values must be required for principal keys #6106

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

We are not currently requiring original values to be saved for principal keys, but the update pipeline uses these values in certain delete scenarios. This causes some saves to fail when using notification entities.
ajcvickers added a commit that referenced this issue Jul 19, 2016
@ajcvickers
Store original values for principal keys
502dc4a 
Update pipeline requires them for certain delete scenarios. Issue #6106

Also add test coverage for changes/fixup using different change notification strategies.
@ajcvickers ajcvickers mentioned this issue Jul 19, 2016
Closed
@ajcvickers ajcvickers self-assigned this Jul 19, 2016
ajcvickers added a commit that referenced this issue Jul 19, 2016
@ajcvickers
Store original values for principal keys
9e0779a 
Update pipeline requires them for certain delete scenarios. Issue #6106

Also add test coverage for changes/fixup using different change notification strategies.
ajcvickers added a commit that referenced this issue Jul 19, 2016
@ajcvickers
Store original values for principal keys
65dd280 
Update pipeline requires them for certain delete scenarios. Issue #6106

Also add test coverage for changes/fixup using different change notification strategies.
@rowanmiller rowanmiller added this to the 1.1.0 milestone Jul 20, 2016
ajcvickers added a commit that referenced this issue Jul 21, 2016
@ajcvickers
Store original values for principal keys
3111677 
Update pipeline requires them for certain delete scenarios. Issue #6106

Also add test coverage for changes/fixup using different change notification strategies.
@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 Jul 21, 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
2 participants
@ajcvickers @rowanmiller