Hi, It looks like Sculptor maps inheritance using the "table per subclass" strategy. This is section 9.1.2 in the Hibernate documentation:
http://www.hibernate.org/hib_docs/reference/en/html/inheritance.html What do you think of adding the option to map using the "table per class hierarchy" strategy (section 9.1.1)? I ask because the table per subclass strategy can be expensive for performance due to all the joins. Since one strategy works best for some cases while the other works better for other cases, it would be nice if Sculptor supports the most common mapping types. Just a thought. Thanks, Polly -- View this message in context: http://www.nabble.com/-Sculptor--mapping-inheritance-using-%22table-per-class-hierarchy%22--tp20138736s17564p20138736.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
