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

Send only dirty values for initial Entity insert #11

Open
tuomur opened this issue May 4, 2017 · 2 comments
Open

Send only dirty values for initial Entity insert #11

tuomur opened this issue May 4, 2017 · 2 comments

Comments

@tuomur
Copy link
Owner

tuomur commented May 4, 2017

Sending full objects with null values sometimes causes problems when server has read-only values or values that cannot be set at initial POST. Might be better to just send dirty values. @awartani already looked at this in #9
@tuomur
Copy link
Owner Author

tuomur commented May 9, 2017 •
edited
Loading

Another solution may be adding support for "Computed" annotations for properties. The metadata may contain elements like <Annotation Term="Org.OData.Core.V1.Computed" Bool="true" /> for this purpose. On POST/PATCH these properties would be dropped from payload.

@tuomur
Copy link
Owner Author

tuomur commented May 10, 2017

Added Computed properties in bf3351a. Might need some more testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tuomur