-
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
Multiple discrimination levels in annotation confuses ORM #9
Comments
That is because this is not supported. |
Thank you for your answer. |
Please move this feature request to www.doctrine-project.org/jira this issue tracker here will be disabled (we dont use it) |
This was referenced Dec 6, 2015
Closed
aldisanta
pushed a commit
to aldisanta/doctrine2
that referenced
this issue
Oct 31, 2016
Kern046
pushed a commit
to Kern046/doctrine-orm
that referenced
this issue
Apr 15, 2022
Disable XSD validation by default
Open
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suppose an inheritance tree like the above:
I want the Gallery/Media discrimination to be on a separated table, so I annotate it in Content.
Likewise, the Video/Image discrimination is annotated in Media to be in the same table.
On updating the schema, the Media table includes every field of Content.
Don't know, maybe I made some mistake and this is not a bug.
Correct me if I'm wrong, please.
More info in:
http://stackoverflow.com/questions/3932505/multiple-discrimination-levels-while-using-doctrine2
The text was updated successfully, but these errors were encountered: