Hi all, I have some questions about polymorphic persistence. Any takers?
I have a schema that currently has about thirty subclasses (more with time) and one common superclass. I am looking for polymorphism between these subclasses. It seems that if I use "table-per-class", I am going to get hit with thirty queries every time I do a select of the superclass, is that correct? But if I use "table-per-subclass" with <joined-subclass/>, I will get two selects -- one for the superclass result set and one for each table (or table type) that exists in the result set. Since most of the collections are of a single subtype, this seems to be the most efficient. True? [a comment: adding a "WildCat" subclass to the documentation example next to "DomesticCat" would be helpful, although it may add unnecessary complexity to the single page manual, since there are no examples of having multiple subclasses with a common parent.] Finally, if I understand the mapping file schema correctly, the superclass mapping file is going to be very very large, essentially containing all of the subclasses in <joined-subclass/> entities. Since the subclass is completely described this way, is the separate mapping file for the subclass redundant? Thanks for any thoughts!! Brian ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
