Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16860 ( https://hibernate.atlassian.net/browse/HHH-16860?atlOrigin=eyJpIjoiY2Y2OW... ) Re: OneToMany with inherited classes on both sides ( https://hibernate.atlassian.net/browse/HHH-16860?atlOrigin=eyJpIjoiY2Y2OW... ) I ran some quick tests and noticed that in both Hibernate 5.6 and 6.1 we used to create the owner_id foreign key column on both the root table computer_system as well as in the 2 subclasses tables customer_computer_system and distributor_computer_system. However, the actual join column used both when persisting and when retrieving the associated entities is only the one in the root computer_system table, that we’re no longer creating in 6.2.5.Final. I suppose we could get rid of the unused columns in the inheritance classes and restore the correct one on the root table. Also, the assertion error you report doesn’t look related but it should be fixed too. ( https://hibernate.atlassian.net/browse/HHH-16860#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16860#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100229- sha1:634ba05 )