Hi, while JDO inheritance strategies offer more flexibility in general than JPA, there appears to be one situation not catered for; namely the JPA strategy of TABLE_PER_CLASS.
I'd propose adding a further JDO strategy of "complete-table" which, when specified on a class means that that class has a table providing columns for all fields of that class and any persistent superclasses. See http://www.datanucleus.org/products/accessplatform_3_0/jdo/orm/inheritance.html Comments ? -- Andy DataNucleus (http://www.datanucleus.org)
