-
Notifications
You must be signed in to change notification settings - Fork 2
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
Change related entity with PUT #1994
Conversation
Suggestion from @GEricson: use two-column table, with request on the left and resulting entities in the right column. |
|
TC 2024-10-09: explicitly state that omitted navigation properties imply no change to the related entities also in PUT requests. |
Change the example to a collection-valued navigation property and point out similarities between contained and non-contained. |
@@ -550,75 +554,81 @@ nested delta representation to: | |||
::: example | |||
Example ##ex: When updating an entity with a 4.01 `PUT` request, the target of a | |||
non-containment navigation property can be replaced without changing either the | |||
old or the new targeted entity itself. The targeted entity can then only be | |||
old or the new targeted entity itself. The targeted entity must then be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replaced without changing either the old or the new targeted entity itself
Foreign-key properties in either the source or the old and new target entities may change as a side-effect.
This text may be misinterpreted as forbidding foreign-key changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only minor nits, see comments
Fixes #1973