Yes, that is a reasonable conclusion, but since the field itself is updated, it is that the "update" manages to bypass the detection of change, and it is difficult for me to figure out where inside Hibernate start digging for that, and hope to have experts look into it.

FTR, I have circumvented this bug by adding the update in onFlushDirty() interceptor which works.