Mapping strategies for representing a class inheritance

I’m french, so excuse me for my poor english :slight_smile:

Is-it possible to choose a mapping strategy to represent a class inheritance ?

It seems the only way supported by DVA is Filtered Mapping by making one only table that contains columns for all attributes of all the abstract and concrete classes. But there are two other ways to do this that could be more efficient in some cases :
Vertical mapping where each class in the tree is mapped to a different table and horizontal mapping where only concrete classes in the tree are mapped to a different table.

I try to do this by adding ORM Implementation stereotype to all classes and generalization links I want to be mapped to a specific table, but a sync from Class diagram to ERD, then from ERD to Class diagram adds incorrect associations between classes into the class diagram.

So, is it possible to do this ?

Thanks,

Antoine