[PR #302] Added failing test case for querying and joining on an associated inheri... #7997

New Issue

admin · 2026-01-22T15:57:52+01:00

admin commented

2026-01-22 15:57:52 +01:00

Original Pull Request: https://github.com/doctrine/orm/pull/302

State: closed
Merged: No

...tance hierarchy

I have written this (partial) failing unit test. When running the test, you'll receive the Semantical Exception as follows:

[Semantical Error] line 0, col 81 near 'idd WHERE idd': Error: Class Doctrine\Tests\Models\Document\ImageDocument has no association named data

I expect that either:

This is expected behaviour. In which case, I'll update the test to expect the semantical exception.
This is a bug (I do hope it is!). In which case, any thoughts on a fix?

Either way, such a query would be great to have in the documentation (including the semantical error), so that when searching for the error, the Doctrine docs appear.

FYI, this has come up from my recent work on trying to find a solution for large inheritance hierarchies (and join limits) and solving the problem by using single table inheritance and associating a "data" class on the base class of the large hierarchy.

P.S. I hope that I do not have a flawed understanding of the ORM and that I'm trying to construct an impossible query/mapping. If so, apologies :)

**Original Pull Request:** https://github.com/doctrine/orm/pull/302 **State:** closed **Merged:** No --- ...tance hierarchy I have written this (partial) failing unit test. When running the test, you'll receive the Semantical Exception as follows: ``` [Semantical Error] line 0, col 81 near 'idd WHERE idd': Error: Class Doctrine\Tests\Models\Document\ImageDocument has no association named data ``` I expect that either: 1. This is expected behaviour. In which case, I'll update the test to expect the semantical exception. 2. This is a bug (I do hope it is!). In which case, any thoughts on a fix? Either way, such a query would be great to have in the documentation (including the semantical error), so that when searching for the error, the Doctrine docs appear. FYI, this has come up from my recent work on trying to find a solution for large inheritance hierarchies (and join limits) and solving the problem by using single table inheritance and associating a "data" class on the base class of the large hierarchy. P.S. I hope that I do not have a flawed understanding of the ORM and that I'm trying to construct an impossible query/mapping. If so, apologies :)

admin added the pull-request label 2026-01-22 15:57:52 +01:00

admin closed this issue

2026-01-22 15:57:53 +01:00

admin referenced this issue

2026-01-22 16:08:35 +01:00

[PR #7997] Update Interface ObjectRepository newer Namespace #10756

Sign in to join this conversation.