@vlad_mihalcea @bsideup @wyhasany By the way, your code still has a few loopholes. Like e.g. serialisation over to another node. Will be completely borked. Same if your logical key contains an ElementCollection or other 1:n or m:n data. There is simply no 100% way to use equals/hashCode *except* to use a UUID.

The High-Performance Java Persistence book and video course code examples - vladmihalcea/high-performance-java-persistence

Introduction As previously explained, using the JPA entity business key for equals and hashCode is always best choice. However, not all entities feature a unique business key, so we need to use another database column that is also unique, as the primary key. But using the entity identifier for equality is very challenging, and this post is going to show you how you can use it without issues. Test harness When it comes to implementing equals and hashCode, there is one and only one rule you should have in mind: Equals and... Read More