We have a composite key where the same column (ccid) is duplicated in three <many-to-one> elements:



Naturally this causes a mapping error (see below) since we have to identify the dominant property by setting the others with .

Problem is, as per the DTD, the <key-many-to-one> element does not allow . In that case, how exactly should we specify the dominant element?

Thought I had found a solution to my problem in this thread: http://forum.hibernate.org/viewtopic.php?t=926346, but there is no solution for a <key-many-to-one> element.

mapping error
--------------


Thanking you all in advance for the help!

Shame on me for not finding that post :(

I just can't believe the support you guys are providing, FAST and accurate, two thumbs way up!

:)

Emmanuel,

We tried to implement what you recommend in the referenced topic http://forum.hibernate.org/viewtopic.php?t=926211&highlight=keyproperty+insert+keymanytoone. However we now receive the following exception:



Our mapping file looks as follow:


I'm afraid we're missing something quite obvious, but we can't seem to put our finger on the problem :(

Anyhow, pointers would be greatly appreciated.

Actually, this is the same issue, you have to key-property tags for each column.
The real good solution is using surrogate keys.

Emmanuel:

quoted from: http://forum.hibernate.org/viewtopic.php?t=92621


Emmanuel,

How then could we implement the workaround you recommended above? I'm still scratching my head over this one...

Something like that


I personnally would have add a generated surrogate key

Hello,

I'm getting the same type of an errot " Repeated column in mapping" for a class that has a composite primary key. One of the columns of the key is the joincolumn of a many-to-relationship.

I'm using JBoss 4.0.1 implementation of the EJB 3.0 spec and there is no way that I can find of setting a Many to One relationship as update/updatable=false, insert/insertable=false.

Not really a Hibernate issue but I thought someone might have a work around.

Thanks.

That's interesting, we probably should avoid that in the spec.

Emmanuel,

Thanks for the response but I'm not sure I understand your answer. What can I do now to get this working?

Thanks.

Either :
- don't use the annotations for this particular case, use hbm.xml instead
- use 2 columns
- use a surrogate key

I know these answers are not really satisfactory

Hi,
I'm also facing the issue like that.

Tables created in MySQL:

CREATE TABLE PARTY (
PARTY_ID INTEGER,
PARTY_TYPE VARCHAR(60) NOT NULL,
CONSTRAINT XPKPARTY PRIMARY KEY (PARTY_ID)
)ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE ROLE (
ROLE_ID INTEGER,
ROLE_TYPE VARCHAR(60) NOT NULL,
CONSTRAINT XPKROLE PRIMARY KEY (ROLE_ID)
)ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE PARTY_ROLE (
ROLE_ID INTEGER,
PARTY_ID INTEGER,
CONSTRAINT XPKPARTY_ROLE PRIMARY KEY (ROLE_ID, PARTY_ID),
CONSTRAINT FK_PARTY FOREIGN KEY (PARTY_ID) REFERENCES PARTY (PARTY_ID),
CONSTRAINT FK_ROLE FOREIGN KEY (ROLE_ID) REFERENCES ROLE (ROLE_ID)
)ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE RELATIONSHIP_RESULT (
ROLE_ID_FROM INTEGER,
ROLE_ID_TO INTEGER,
RELATIONSHIP_RESULT VARCHAR(60) NOT NULL,
CONSTRAINT XPKRELATIONSHIP_RESULT PRIMARY KEY (ROLE_ID_FROM, ROLE_ID_TO)
)ENGINE=InnoDB DEFAULT CHARSET=latin1;

CREATE TABLE RELATIONSHIP (
MEMBERSHIP_ID INTEGER,
RL_PARTY_ID_FROM INTEGER NOT NULL,
RL_ROLE_ID_FROM INTEGER NOT NULL,
RL_PARTY_ID_TO INTEGER NOT NULL,
RL_ROLE_ID_TO INTEGER NOT NULL,
CONSTRAINT XPKRELATIONSHIP PRIMARY KEY (MEMBERSHIP_ID),
CONSTRAINT FK_ROLE_FROM FOREIGN KEY (RL_ROLE_ID_FROM, RL_PARTY_ID_FROM) REFERENCES PARTY_ROLE (ROLE_ID, PARTY_ID),
CONSTRAINT FK_ROLE_TO FOREIGN KEY (RL_ROLE_ID_TO, RL_PARTY_ID_TO) REFERENCES PARTY_ROLE (ROLE_ID, PARTY_ID),
CONSTRAINT FK_RELN_RESULT FOREIGN KEY (RL_ROLE_ID_FROM, RL_ROLE_ID_TO) REFERENCES RELATIONSHIP_RESULT (ROLE_ID_FROM, ROLE_ID_TO)
)ENGINE=InnoDB DEFAULT CHARSET=latin1;

Using Hibernate tools to generate the hbm and pojo files.

In Relationship.hbm.xml shows:

<class name="com.cts.dao.pom.Relationship" table="relationship" catalog="test">
<comment></comment>
<id name="membershipId" type="int">
<column name="MEMBERSHIP_ID" />
<generator class="assigned" />
</id>
<many-to-one name="partyRoleByFkRoleTo" class="com.cts.dao.pom.PartyRole" fetch="select">
<column name="ROLE_ID_TO" not-null="true">
<comment></comment>
</column>
<column name="PARTY_ID_TO" not-null="true">
<comment></comment>
</column>
</many-to-one>
<many-to-one name="relationshipResult" class="com.cts.dao.pom.RelationshipResult" update="false" insert="false" fetch="select">
<column name="ROLE_ID_FROM" not-null="true">
<comment></comment>
</column>
<column name="ROLE_ID_TO" not-null="true">
<comment></comment>
</column>
</many-to-one>
<many-to-one name="partyRoleByFkRoleFrom" class="com.cts.dao.pom.PartyRole" update="false" insert="false" fetch="select">
<column name="ROLE_ID_FROM" not-null="true">
<comment></comment>
</column>
<column name="PARTY_ID_FROM" not-null="true">
<comment></comment>
</column>
</many-to-one>
</class>

In the <many-to-one name="partyRoleByFkRoleTo" tag there is no attributes having insert="false" update ="false"

but in the same table the other reference for <many-to-one name="partyRoleByFkRoleFrom tag there it having the attibutes insert="false" update ="false".

We can able to insert partyRoleByFkRoleTo object in to Relationship table but cannot able to insert partyRoleByFkRoleFrom object in to Relationship table. How we insert the both the object in to the Relationship table?