Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-937

doctrine-mapping.xsd sequence relation-entities

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor 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.

        Activity

        Leon van der Ree created issue -
        Guilherme Blanco made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Roman S. Borschel [ romanb ] Guilherme Blanco [ guilhermeblanco ]
        Fix Version/s 2.3 [ 10185 ]
        Resolution Fixed [ 1 ]
        Benjamin Eberlei made changes -
        Workflow jira [ 12233 ] jira-feedback [ 14694 ]
        Benjamin Eberlei made changes -
        Workflow jira-feedback [ 14694 ] jira-feedback2 [ 16558 ]
        Benjamin Eberlei made changes -
        Workflow jira-feedback2 [ 16558 ] jira-feedback3 [ 18811 ]

          People

          • Assignee:
            Guilherme Blanco
            Reporter:
            Leon van der Ree
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: