Closed aradalvand closed 9 months ago
Duplicate of #28766 and #32058
The workaround for #32058 mentioned in this comment doesn't actually work for JSON columns, because of #28766, but then even if #28766 was implemented, that alone would still not solve the problem because it wouldn't work for collections (e.g. the Product.Traits
in the example above).
So, am I right in thinking that this means #32058 isn't just a nice-to-have, but pretty crucial?
Currently, there seems to be no actual workaround for this, ExecuteUpdate
simply doesn't work on JSON columns. Right?
Does that mean we have to resort to traditional change-tracking-style updates for JSON columns for now?
@aradalvand Correct, the bulk update APIs currently do not support updating JSON columns.
I couldn't find an existing for this, let me know if there is one.
I was surprised to find out that
ExecuteUpdate
doesn't seem to work at all on the new JSON columns. It doesn't work on individual properties on the JSON document, nor does it work on the entire column (which should've been straightforward to implement), nor does it work on JSON collections. Is this expected?!Repro:
Program.cs
:The
.csproj
file:The exception details: