Hibernate Community • View topic - One-to-one mapping with composite id

View unanswered posts | View active topics

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

One-to-one mapping with composite id

Page 1 of 1

[ 5 posts ]

Previous topic | Next topic

Author

Message

toppac

Post subject: One-to-one mapping with composite id

Posted: Tue Jun 15, 2004 3:58 pm

Newbie

Joined: Tue Jun 15, 2004 3:52 pm
Posts: 4

Having some difficulty figuring out how to correctly map my tables. The table structure is as follows

Code:

Table A {
   key{
     prop1
     prop2
     prop3
  }
}

Table B {
  key {
    prop1
    prop2
  }
}

Table A has a 3 property composite key and table B has a 2 property composite key. Their relationship falls on prop1 and prop2 from each table. I've read the documentation about how to define a one-to-one mapping but I can't figure out how to do the mapping with composite keys that have different number of properties.

Top

david

Post subject:

Posted: Wed Jun 16, 2004 2:45 am

Hibernate Team

Joined: Tue Aug 26, 2003 7:19 pm
Posts: 2364
Location: Brisbane, Australia

Sorry you cannot do - they need the same key.

Top

david

Post subject:

Posted: Wed Jun 16, 2004 2:45 am

Hibernate Team

Joined: Tue Aug 26, 2003 7:19 pm
Posts: 2364
Location: Brisbane, Australia

You will be able to do a many-to-one though

Top

etienne

Post subject:

Posted: Fri Jul 29, 2005 1:45 pm

Senior

Joined: Tue Jan 11, 2005 5:03 pm
Posts: 137
Location: Montreal, Quebec

I also have this kind of issue.

Even with a key componentId, It is not possible to do a one-to-one relationship ?

Code:

<composite-id name="id"
   class="TableBId">
   <key-property name="prop1"
      <column name="prop1"/>
   </key-property>
   <key-property name="prop2"
      <column name="prop2"/>
   </key-property>
</composite-id>

Table A {
key{
TableBId
prop3
}
}

Table B {
key {
TableBId
}
}

Thanks

Etienne.

Top

etienne

Post subject:

Posted: Fri Jul 29, 2005 2:19 pm

Senior

Joined: Tue Jan 11, 2005 5:03 pm
Posts: 137
Location: Montreal, Quebec

I just realized that. My post is a non-sense.

If the prop3 doesn't descriminate on the object, it should not be part of the primary key! In the other side, if it must be part of the primary key (to descriminate the object), in means that you have a one-to-many relationship.

Etienne
Montreal

Top

Page 1 of 1

[ 5 posts ]

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum