Skip to content

Loading…

DDC-3076: [GH-1006] Handling invalid discriminator values #3849

Closed
doctrinebot opened this Issue · 3 comments

2 participants

@doctrinebot

Jira issue originally created by user @doctrinebot:

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

Url: #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.

@doctrinebot

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1006] was closed:
#1006

@doctrinebot

Comment created by @ocramius:

Merged: 2da74e5

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot doctrinebot added this to the 2.4.3 milestone
@doctrinebot doctrinebot closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.