Hello,

i am in the situation that i have an m:n relationship between two entities. I know, if i want to have mapping attributes i should spezify an mapping table entity where i can places these and make an m:1 <-> mapping-table <-> 1:n relation instead.

But what is when an application is grown with an m:n relation, and then you discover the need of an mapping-table-attribute?

Redisign has a hight risk and will have a lot of effort.

What is the best practice to handle these situation?

Is'nt it an important missing feature in hibernate to map mapping-table-attributes with an m:n relation?


Thanks forward and Greatings to the community