Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-3076

[GH-1006] Handling invalid discriminator values

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5, 2.4.3
    • Component/s: None
    • Security Level: All
    • Labels:
      None

      Description

      This issue is created automatically through a Github pull request on behalf of Trainmaster:

      Url: https://github.com/doctrine/doctrine2/pull/1006

      Message:

      Two scenarios:

      • *The DiscriminatorMap is specified via metadata*. In case the entity's discriminator value is not matching with a value of the DiscriminatorMap it will result in a ``Notice: Undefined index ... on line 102`` and ``exception 'Doctrine\Common\Persistence\Mapping\MappingException' with message 'Class '' does not exist' in``. The proposed changes deal with this.
      • *The DiscriminatorMap is automatically generated*. The discriminator value may no longer be invalid if there's just metadata missing for the automatically generated class names. I'm not sure how to deal with that properly.

        Activity

        Hide
        Doctrine Bot added a comment -

        A related Github Pull-Request [GH-1006] was closed:
        https://github.com/doctrine/doctrine2/pull/1006

        Show
        Doctrine Bot added a comment - A related Github Pull-Request [GH-1006] was closed: https://github.com/doctrine/doctrine2/pull/1006
        Show
        Marco Pivetta added a comment - Merged: https://github.com/doctrine/doctrine2/commit/2da74e5147b6babf296ccdca30931525cbbc3cac

          People

          • Assignee:
            Guilherme Blanco
            Reporter:
            Doctrine Bot
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: