-->
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.  [ 1 post ] 
Author Message
 Post subject: ORM design question: Weak Entity Primary Key
PostPosted: Mon Jul 25, 2005 8:09 am 
Newbie

Joined: Thu Mar 25, 2004 1:43 pm
Posts: 3
Hi,

For some time I´ve been using surrogate keys for identifying all entities in my database. Although this sounds logical to me when applied to the main entities in my domain model, it does not seem to add much for weak entities, which will carry the key generated for their owning entities and will always be referenced through the main entity. These weak entities have 'component' collection semantics.
I am thinking about mapping these 'components' to a table without a surrogate key, making the foreign key and a sequence number, relative to this foreign key, the component PK. As this is also not best practice (using composity keys to identify the entity) I would like to know if anyone in the list could share their thoughts about this or any similar approachs.

TIA,

Tedi


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

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.