-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] Fix cannot select FOR UPDATE from view on Oracle #45714
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
[Messenger] Fix cannot select FOR UPDATE from view on Oracle #45714
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 |
I'd trust you on this one as I don't use Oracle. I don't have a better idea, code wise, so I'm fine with this approach. |
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.
I've actually rebased on 4.4. I'm merging now but please follow up with tests if you can.
Thank you @rjd22. |
@nicolas-grekas I will add some tests for this within a week. |
@nicolas-grekas Tests added in #45966 |
… (rjd22) This PR was merged into the 4.4 branch. Discussion ---------- Add tests to messenger connection get for OraclePlatform | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | no | New feature? | no | Deprecations? | no | License | MIT Add tests for Oracle for code added in #45714 Commits ------- 6d5887c Add tests to messenger connection get for OraclePlatform
I realize this solution is quite getto. I hope to get some feedback on it so we can solve this oracle issue properly but ATM this is a good starting point to reach a proper solution.
For this reason I didn't add tests yet.
What happens is that Oracle doesn't like query's that combine ROWNUM and FOR UPDATE. To solve this the query needs to be wrapped in a subquery that limits the results by ID so:
becomes:
I don't really know another way to solve this better. But feel free to nitpick at my solution.