-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Symfony Messenger - ORA-02014: cannot select FOR UPDATE from view #33718
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
Comments
If I don't miss anything, we don't build the SQL ourselves but rely on Doctrine DBAL for that. Thus, I am not sure there is anything we can do or if this shouldn't be reported to the Doctrine project instead. |
Could you try next release now #32427 is merged? |
Let's close here for now. We can still reopen if it turns out that #32427 isn't enough. |
This bug is still not solved. (Symfony 5.0.6) |
Hey, thanks for your report! |
Could I get an answer? If I do not hear anything I will assume this issue is resolved or abandoned. Please get back to me <3 |
Hey dear bot it's not resolved |
Hey, thanks for your report! |
Hello? This issue is about to be closed if nobody replies. |
Hello |
@bohanyang Would you like to try to solve this issue? |
Sure but maybe we have to write a SQL specific to Oracle to solve this issue. |
This issue still exists with Oracle and the latest Dbal driver. To solve this the query needs to be written in the following way:
What would be the correct way to solve this for symfony/messenger? Make a separate OracleConnection like is done with Postgresql ? |
Symfony version(s) affected: 4.3
Description
In AbstractOracleDriver.php line 57:
In OCI8Exception.php line 16:
How to reproduce
Use oracle12 with symfony 4.3 and messenger
Was affected with this issue too: #32427
Fixed it by removing the "T" from that dateformat
I think the query must be rewritten, so that the rownum filter is not on the outer sql. Maybe like this? https://stackoverflow.com/a/6337356/1953421
Could not try, because i do not know where to change the sql for the messenger select.
The text was updated successfully, but these errors were encountered: