-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix OneToManyPersister::deleteEntityCollection missing discriminator column/value. (GH-11500) #11501
Conversation
It seems there are CI jobs failing. Please take a look at this guide for more on how to handle those. |
Thanks! Ran the code-beautifier, checked with codesniffer and static analysis tools and pushed amendments. |
/** | ||
* @throws EntityNotFoundException | ||
* @throws MappingException | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This replaces DBALException with ORMExceptions. Is this an additional fix because none of them extends the Exception of DBAL?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DBALException should not have been removed - my IDE autofix appears to have removed that line by mistake. I have pushed an amendment to fix that.
The ORM exceptions are potentially thrown by UnitOfWork::getEntityIdentifier()
(EntityNotFoundException) and ClassMetadataInfo::getFieldForColumn()
(MappingException).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this is a breaking change as this is going to be merged up to 3 and 4 of ORM. But it looks like the DBALException isn't handled either by ORM despite being an Exception of a different library. Now ORMExceptions were added too.
Fixes #11500
This issue may exist in 3.x and 4.x, I haven't yet had a chance to test. If so I can create seperate pull requests for those branches.