…lumns (juanmiguelbesada)This PR was squashed before being merged into the 3.4 branch.Discussion----------[DoctrineBridge]  indexBy could reference to association columns| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Tickets       |Fix#37982 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->| License       | MIT| Doc PR        | -<!--Replace this notice by a short README for your feature/bugfix. This will help peopleunderstand your PR and can be used as a start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Never break backward compatibility (seehttps://symfony.com/bc). - Bug fixes must be submitted against the lowest maintained branch where they apply   (lowest branches are regularly merged to upper ones so they get the fixes too.) - Features and deprecations must be submitted against branch 5.x.-->This is my approach to solve#37982. It partials reverts@xabbuh PR#38604This is my first Symfony contribution, so please, tell me if I need to do something more or something is wrong.Also, this bug affects 4.x and 5.x versions. I think merging in this branches is done automatically. If not, please tell me.Thanks youCommits-------f9a0e00 failing test for issue 388614c36145 [DoctrineBridge]  indexBy could reference to association columns