Rong, >We use "table per class hierarchy" strategy to map inheritance. For the >ItemStructure attribute of Party, just declare a "many-to-one" and >hibernate will take care of the rest ;)
Does that mean you use a single table to map the data value class hierarchy? If so how do you handle generics? Do you also have different columns for each of instance of the generic type? Do you use eager loading through Hibernate or lazy loading? Do you have any indication on performance using this approach? cheers </jima> - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
