Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: Git Master
-
Fix Version/s: 2.3
-
Component/s: Mapping Drivers
-
Security Level: All
-
Labels:None
Description
I noticed some problems with
the doctrine-mapping.xsd (which apparently is not used to validate the
mapping, but only provided to support code completion in your xml-
editor)
The order in which you define the elements like cascade and join-
column(s) for the relation-entities is currently important since it is
a sequence, but is this really desired? Why force this order? defining
cascade before join-column would make perfect sense as well, doesn't
it.
Is this issue still valid in the latest Doctrine (trunk)? It doesn't seem to be.