We just hit the same issue, but using @ManyToMany with 5.2.17.Final. I can't believe this issue is marked as minor and is still open after 7 years This is definitely not a minor issue - duplicate rows in the database can easily break business logic.