I have a base class that most of my persistent classes extend. In some cases, the final class is three or four levels down (i.e. Foo2 extends Foo1 extends FooBase). My database schema is such that I have to go with the subclass-per-table strategy.
In situatations where I do not know the final class and I have to do a session.load(FooBase.class, id), Hibernate has to generate a huge join of all possible subclass tables (or at least, that's what it looks like it's trying to do). I was wondering if it might not be
possible to provide a hint to Hibernate, something along the lines of the discriminator that <subclass> uses so that Hibernate can figure out which tables to grab?
Thanks, -Mark
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
