You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bug #46 SuperClass AbstractClient can not have indentifier mapped (yoshz)
This PR was merged into the 0.1-dev branch.
Discussion
----------
SuperClass AbstractClient can not have indentifier mapped
This is a fix for bug #45.
Turns out that AbstractClient is wrongly mapped.
Quoted from [Doctrine/ORM documentation](master...yoshz:bugfix/docrine-mapping):
> A mapped superclass cannot be an entity, it is not query-able and persistent relationships defined by a mapped superclass must be unidirectional (with an owning side only). This means that One-To-Many associations are not possible on a mapped superclass at all. Furthermore Many-To-Many associations are only possible if the mapped superclass is only used in exactly one entity at the moment. For further support of inheritance, the single or joined table inheritance features have to be used.
So AbstractClient can not have an identifier and can not be used as an association between entities.
Commits
-------
b91268b SuperClass AbstractClient can not have indentifier mapped
0 commit comments