On 15 Nov (21:14), Les A. Hazlewood wrote: > Are you implying I need a <subclass> definition for each of the above 3 classes? > Doesn't this mean there would be 3 tables created, one for each of them?
No, this is a different strategy, it's called "table per class hierarchy", not "table per concrete subclass". > I suppose I _could_ use a <subclass> mapping per class (if that is required), > but that doesn't make sense to me: If I want to persist 15 different permission > types, there would be 15 tables created each defined with the exact same data You are wrong. You need one table and a discriminator column. Read some of the Scott Ambler papers and the Hibernate documentation. -- Christian Bauer [EMAIL PROTECTED] ------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
