Closed yoshizaki-aill closed 6 months ago
Maybe related to https://github.com/Dynamoid/dynamoid/issues/666 ?
Yes, it seems a symptom of the same issue. Mutated collection/custom type isn't detected as a field change at persisting.
Sorry for creating a duplicate issue. I understood that this is an issue due to a differential update. I certainly think this is a difficult problem. The affected parts of our source code have been fixed, so there is no problem.
Thank you.
I'm trying to upgrade Dynamoid
3.8.0
to3.10.0
. Then, there was a case where the array field could not be updated. (Also, themap
type is the same.)Field definition:
The following case cannot be saved. This looks confusing.
It works if I replace the whole (duplicated) array. However, this can be inconvenient for coding.