-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DoctrineBridge] Take into account that indexBy="person_id" could be a db column name, for a referenced entity #39667
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
[DoctrineBridge] Take into account that indexBy="person_id" could be a db column name, for a referenced entity #39667
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
Could you add a testcase? |
@OskarStark Sure -- just noticed I had missed that part, but got distracted with new years stuff! ... will try and get one up shortly. |
Thank you 😊 |
c877884
to
a3fa8e1
Compare
a3fa8e1
to
bd3fe22
Compare
Now rebased for 4.4 |
@victormacko Can you have a look at the tests as they seem to be broken by your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
once tests are fixed
Done @fabpot .. let me know if there's anything I can do to help with the other failing tests - one is a class-ref issue, and another due to commits (both of which i'm not sure about how to assist with) |
@victormacko Something went wrong here as there are many unrelated changes. Can you rebase on the current 4.4 branch? |
f3610f3
to
1e2367d
Compare
…a db column name, for a referenced entity
1e2367d
to
472eab1
Compare
Thank you @victormacko. |
Nps, thanks @xabbuh -- not sure what happened either, but appreciate your help :) |
unfortunately this issue still persists in 5.4.10 if Example:
any ideas? |
@da-anda please open a new ticket instead of commenting on a PR merged more than 1 year ago. Otherwise, the only way to find back the discussion is through notifications (as nobody goes checking old merged PRs for new comments), and not everyone gets notifications for all new comments. |
done |
In Symfony 4.4.17 (I think), using ManyToMany in doctrine, along with indexBy="person_id" (in the related entity, which has a property of "id" (which in-turn uses the db column "person_id" worked as expected. When upgrading to Symfony 5.2.1, this stops working.
This change continues on from issue #37982 to fix a further edge case.