-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Document class is unlisted in the discriminator map - using no discriminator map #2002
Comments
Could you by any chance reproduce this in a test case? You can find a whole bunch of such test cases in https://github.com/doctrine/mongodb-odm/tree/master/tests/Doctrine/ODM/MongoDB/Tests/Functional/Ticket. Thanks! |
Will give it a shot. |
Done. I hope the clearing loaded metadata like that is okay. It simulates my problem where request that doesn't work with document A but works with document B fails. |
Until the bug is fixed, I forked the ODM and just plainly disabled the exception whatsoever to enable me to work on my project. |
Fix has been merged to 1.3 and master. Thanks for reporting, and more so for the failing test case! |
The exception went away, but a new problem appeared. See: #2024 |
Bug Report
Summary
Document class "Domain\XYZ\Document" is unlisted in the discriminator map although I am using no discriminator map.
Possibly related to this: #867
Current behavior
Let's assume this code:
Now I get the
Document class "DocumentA" is unlisted in the discriminator map
exception on a flush.The interesting fact is that when I create the $docA in the same script as the $docB everything works.
However when I load it from the database prior setting it to the property, I get the exception.
The text was updated successfully, but these errors were encountered: