-->
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: Query
PostPosted: Wed Dec 13, 2006 4:05 am 
Beginner
Beginner

Joined: Mon Mar 14, 2005 9:07 am
Posts: 27
Hi,

What constraints should be kept in mind while deciding whether to use a single Table in inheritence (using a discriminator) and single table per subclassing.

Any advice?

Thanks in advance.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Dec 13, 2006 9:40 am 
Regular
Regular

Joined: Wed Mar 23, 2005 8:43 am
Posts: 105
Location: Moscow, Russia
Main disadvantage of the table-per-class hierarchy strategy is that columns specific for subclass must be nullable, but this strategy performs better than tabe-per-subclass strategy. Main disadvantage of the tabe-per-subclass strategy is that it uses additional join wich may affect on perfomance.

_________________
Best Regards


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.