I have tried and ask the same question on StackOverFlow but it seem no help. https://stackoverflow.com/questions/57283004/dynamicupdate-added-extra-untouched-column-in-update-statement?noredirect=1#comment101061876_57283004
I think there is some problem down the code but not very sure how to really pinpoint the problem.
I am facing a weird behavior using @DynamicUpdate with one of my entity. So my entity is defined like this
`DOTimestampConverter` is just a simple `AttributeConverter` to convert `ZonedDateTime` to ms for me to store in DB as number.
As you can see I marked the entity with `@DynamicUpdate`.
I have a small jersey REST-API which allow me to update all of the normal field beside the id and the generated date. I always check if the input is `null` before actually touching the setter for the field.
I see a very weird behavior with the column `address_city`, it would be included in every update like this even if I only touch other fields, in this case, just the `name` which translate to `court_name` because `name` is a reserved keyword in sql. *UPDATE* Actually the problem is not with just the `address_city` collumn. Even if I ignore that column, other column would get included in the update statement.
Where as if I only edit the `address_city` only then I would see it correctly
Did anyone face this problem before?
The stack I am using are
And the data schema
This is how update through REST-API