An extra UPDATE is triggered when using records

[dyleph]

No description provided.

[vladmihalcea]

Thanks. It's much better. I'll check it out tonight.

[dyleph]

Thank you @vladmihalcea . Sorry for late. Because I was in my holiday since Friday :)
Have a nice day!

[vladmihalcea]

Likewise

[vladmihalcea]

The problem comes from the areEqual method which finds different internal Map types.

[dyleph]

Is this problem from hypersistence-utils?

[vladmihalcea]

If you replace the record with a POJO that has equals and hashCode, it will work.

I will see how to accommodate a fix when I get some time.

[dyleph]

Hi @vladmihalcea ,
Do we have any updates with this issue?

Regards,
Dy

[vladmihalcea]

@dyleph This is a very complex issue, and you are better off using JsonNode or type-safe POJOs on the entity attribute that maps the JSON if you want to avoid it.

I'm not sure when I'll have time to fix it since the problem is caused by records that can be contained on any hierarchical level in a Map of Map structure you're now using.

But, as long as you have some workarounds, you should those instead.