-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: composite element vs two 1-N relations
PostPosted: Mon Aug 02, 2004 8:27 am 
Newbie

Joined: Mon Aug 02, 2004 8:15 am
Posts: 1
I encountered unanswered questions to the questions I am very interested in too somewhere on the forum.

What differences (in comparing the two 1-N with composite element) would it made to the system, in terms of performance and difficulty on maintaining data?

Now, if I have my own primary key for the join table how should I describe it using composite element mapping?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Aug 02, 2004 8:30 am 
Hibernate Team
Hibernate Team

Joined: Mon Aug 25, 2003 9:11 pm
Posts: 4592
Location: Switzerland
You can use an <idbag> with a <collection-id>.

_________________
JAVA PERSISTENCE WITH HIBERNATE
http://jpwh.org
Get the book, training, and consulting for your Hibernate team.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

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

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.