-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[doctrine-messenger] Error only Oracle database ORA-01008 #52570
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
Labels
Comments
Thank you for the report. Can you please check if #52581 would fix your issue? |
nicolas-grekas
added a commit
that referenced
this issue
Nov 14, 2023
This PR was merged into the 5.4 branch. Discussion ---------- [Messenger] attach all required parameters to query | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #52570 | License | MIT Commits ------- 38a4125 attach all required parameters to query
Thanks, its correct. |
Thank you for the feedback! 👍 |
xabbuh
added a commit
that referenced
this issue
Dec 1, 2023
This PR was merged into the 5.4 branch. Discussion ---------- add parameter types in query builder | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | | License | MIT fix last update, required parameter types in query builder. #52570 Commits ------- abd3a9e add parameter types in query builder
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
6.3.0
Description
When execute command php bin/console messenger:consume async, return error database ORA-01008
How to reproduce
install symfony 6.3
configure symfony messenger with transport doctrine oracle
Possible Solution
Variable $query is override in platform oracle.
https://github.com/symfony/doctrine-messenger/blob/6.3/Transport/Connection.php#L184
$query original contains parameters need.
https://github.com/symfony/doctrine-messenger/blob/6.3/Transport/Connection.php#L214
Additional Context
No response
The text was updated successfully, but these errors were encountered: