Entity gets updated when a query is performed. Dirty check changes

We didn't mention this in the migration guide because this was a bug fix. You can search for the Jira issue if you want, but ORM wasn't flushing changes even if the json data was changed before this fix.

can be closed. i don’t have the rights to do that

I see. This explains it

I checked only the migration guide from 6.3 to 6.6 to see if there is something specified about the JsonJavaType and I also saw that the dirtyCheck mechanism was also changed between 6.3 and 6.6 but didn’t look that deep.

Would have been good maybe to have a mention of this in the migration guide as this can cause issues but it’s also my fault for not implementing hashcode and equals.

Thanks for looking into this further.

I looked further and found where the behavior difference comes from. When you first persist the Prescription entity, Hibernate builds an internal snapshot of its state. In 6.3.1, BasicCollectionJavaType was used which preserved reference equality during deep copy (see this), so the snapshot contained the same ValidationMessageError instance. In 6.6.2, JsonJavaType is used which creates new instances during deep copy (see this). Knowing this explains why Hibernate detects "changes" when comparing against the snapshot in 6.6.2, even though the actual data hasn't changed.

I can confirm that adding a equals doesn’t crash the junit test anymore and hibernate doesn’t consider Prescription as dirty.
When I debugged, the validationMessages from the Invoice query, they came back null so I assumed that it compares null with what is in the database.

Seems that is not the case.
Thanks for looking into this.

Although it is strange that hibernate 6.3.1 did not have any issue with this, isn’t it ?