Andrus Adamchik <andru..bjectstyle.org> wrote:
> Also I agree that doing the "transparent" vertical inheritance maybe lots
> of work... but this is work to support flattened atributes really, nothing
> beyond that. And there will be no need to select "type" of inheritance, as
> it will work just like the single table variety.
Single-table inheritance and composite vertical-inheritance aren't
compatible in the current modeler.
#0, the superclass is hardcoded to the wrong value -- my use cases are
simple enough I could get around this by always using the DataMap superclass
in my verti templates.
#1, ObjRelationship.getDbEntity() returns the wrong DBEntity (and breaks
ObjRelationship.refreshFromPath()). This is why I'm unable to determine the
path to the parent entity.
/**
* Returns a DbEntity associated with this ObjEntity.
*/
public DbEntity getDbEntity() {
// since 1.2 - allow overriding DbEntity in the inheritance
hierarchy...
if (dbEntityName != null) {
return getNonNullNamespace().getDbEntity(dbEntityName);
}
ObjEntity superEntity = getSuperEntity();
if (superEntity != null) {
return superEntity.getDbEntity();
}
return null;
}
This archive was generated by hypermail 2.0.0 : Wed Jun 15 2005 - 17:13:44 EDT