Not tried out, but from reading the specification of ClassMetadataInfo: when setting a Class Table inheritance via PHP you don't use addInheritedAssociationMapping ( ), but only setInheritanceType<http://www.doctrine-project.org/api/orm/2.4/source-class-Doctrine.ORM.Mapping.ClassMetadataInfo.html#1943-1958>(),
setDiscriminatorColumn<http://www.doctrine-project.org/api/orm/2.4/source-class-Doctrine.ORM.Mapping.ClassMetadataInfo.html#2529-2565>() and setDiscriminatorMap<http://www.doctrine-project.org/api/orm/2.4/source-class-Doctrine.ORM.Mapping.ClassMetadataInfo.html#2567-2580> (). A bit confusing could be the names used by Doctrine for the inheritance types: Doctrine uses JOINED for Class Table inheritance and TABLE_PER_CLASS for Concrete Table inheritance. The latter could better have been called TABLE_PER_OBJECT or TABLE_PER_ENTITY, for the superclass doesn't have its own table when using Concrete Table inheritance. But that is how things evolve. A good thing of Doctrine is that it tries to keep backwards compatibility as much as possible, but that also means that some less well chosen names are preserved in later versions -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
