Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-2721

CLONE - doctrine-mapping.xsd sequence relation-entities

    Details

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

      I looked in the repository and it seems xsd is not valid for all branches 2.1.x, 2.2, 2.3.4, 2.4.0-RC2 and master

        Activity

        Benoît Burnichon created issue -
        Benoît Burnichon made changes -
        Field Original Value New Value
        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.
         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.

        I looked in the repository and it seems xsd is not valid for all branches 2.1.x, 2.2, 2.3.4, 2.4.0-RC2 and master

          People

          • Assignee:
            Guilherme Blanco
            Reporter:
            Benoît Burnichon
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: