You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could apply the same logic we're discussing for SaveChanges:
Do "least-common-denominator" to find the smallest branch containing all the properties to be updated.
As a further optimization, nest multiple invocations (e.g. of JSON_MODIFY for SQL Server) to update the two properties; but we need to investigate and benchmark to know to what extent that makes sense and when.
The text was updated successfully, but these errors were encountered:
@nasisakk your Entry type seems to be a top-level entity type (as it's directly on the context), and therefore not an actual JOSN owned entity - so this doesn't seem relevant... It's also hard to see how having [JsonIgnore] would change anything here.
Can you please open a separate issue with a runnable, minimal code sample?
Things get interesting when there are multiple updates inside the same JSON document:
We could apply the same logic we're discussing for SaveChanges:
The text was updated successfully, but these errors were encountered: