-
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
Add regression test for #8108 #11523
base: 3.2.x
Are you sure you want to change the base?
Conversation
Ok I've debugged the issue, that lies in
Any suggestion on how we should fix this? [EDIT] In short, it seems that the issue stems from the fact that I'm having this chain of inheritance:
|
Bisecting and using this as the reproducer, I've discovered that my chain of inheritance was considered "bad" but accepted in 2.x only thanks to the Should I consider this as invalid and close? |
By what? The schema validator? If yes, then we should probably close, and I think we might want to work on making it impossible to write regression tests for an invalid schema 🤔 |
Locally, the schema validator is what led me to this reproducer, but it's an exception, not a validation error. This reproducer, ported to the 2.x branch, fails if
|
Then it might be to severe to merely be marked as invalid only to be allowed later on. |
As reported in #8108 (comment), this is a regression test for a bug that I encounter when upgrading from ORM 2 to 3. I'm not sure how this should be fixed.
[EDIT] I should add that this doesn't happen if the relation is coming from a trait instead of an abstract class.