-->
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: Table per concrete class with unions: limitations?
PostPosted: Sun Dec 21, 2008 6:27 am 
Beginner
Beginner

Joined: Thu Jun 07, 2007 2:38 am
Posts: 28
Location: Italy, Rome
In our application we have this structure:
(1) inheritance hierarchy is :Table per concrete class with unions
(2) class B extends abstract class A
(3) B has an one-to-many relationship to A

While testing CRUD on B, there is an error that table A does not exist.

My questions are:
(A) why is Hibernate asking for table A? With the chosen inheritance type it shouldn't
(B) is the relationship in (3) valid?
(C) should we change inheritance hierarchy?

Please provide some light!


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.