Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-138

Allow for mixed inheritance mapping

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: DQL, Mapping Drivers, ORM
    • Security Level: All
    • Labels:
      None

      Description

      Requesting implementation of mixed inheritance mapping (class table inheritance and single table inheritance).

      This would be especially handy when the difference between certain classes is only "implementational" (i.e. a subclass only functions differently/implements abstract methods and does not specify any additional fields). Using class table inheritance would result in tables only containing an id column.

        Issue Links

          Activity

          Reinier Kip created issue -
          Roman S. Borschel made changes -
          Field Original Value New Value
          Affects Version/s 2.0 [ 10021 ]
          Fix Version/s 2.1 [ 10022 ]
          Roman S. Borschel made changes -
          Link This issue is duplicated by DDC-265 [ DDC-265 ]
          Benjamin Eberlei made changes -
          Affects Version/s 2.0 [ 10021 ]
          Roman S. Borschel made changes -
          Fix Version/s 2.1 [ 10022 ]
          Benjamin Eberlei made changes -
          Workflow jira [ 10399 ] jira-feedback [ 13837 ]
          Benjamin Eberlei made changes -
          Workflow jira-feedback [ 13837 ] jira-feedback2 [ 15701 ]
          Benjamin Eberlei made changes -
          Workflow jira-feedback2 [ 15701 ] jira-feedback3 [ 17958 ]

            People

            • Assignee:
              Roman S. Borschel
              Reporter:
              Reinier Kip
            • Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: