Jim Alateras wrote: > 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?
We hide the DataValue as the root class of all data types and use one table for each concrete data type and its subclasses. Generics is not yet supported by hibernate directly, so we use "any" tag to handle generics for the time being. > > Do you use eager loading through Hibernate or lazy loading? Eager loading is OK for our application since we always need to load a whole Composition. > > Do you have any indication on performance using this approach? It seems to be reasonable as far. > > cheers > </jima> > > - > If you have any questions about using this list, > please send a message to d.lloyd at openehr.org > - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
