-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
2.6.4. breaks queries using objects as parameters #7827
Comments
This should indeed not be converted to identifiers, since you're binding a string array, yet declared |
Might be true… I am quite sure we did add that parameter hint on purpose, and it worked before. So… I'll try to fix that. |
Can you maybe come up with a test case verifying your use-case (that is green on |
This "fixes" doctrine/orm#7827, by actually passing the correct type as parameter. And the "type hint" can be removed, as well.
I'll try the test-case, but removing the wrong parameter type hint or actually passing an array of strings solves the issue for our code. So I guess it's really a "side-effect we used so far" that has been removed. Too bad I cannot remeber what we actually fixed back then by adding it… |
@kdambekalns should we close this issue, then? |
Feel free, if I come around to creating a valid test case, I'll let you know. Thanks! |
This "fixes" doctrine/orm#7827, by actually passing the correct type as parameter. And the "type hint" can be removed, as well.
I've outlined this issue in more detail in #7832. In v2.6.3, the $type was verified before being used, where in v2.6.4, the $type is blindly accepted without type-checking. |
This is the correct/expected behavior |
2.6.4 introduced bc breaking change. This code worked in 2.6.3 and befire. Now it fails
This change is causig this:
|
@szambonurek can you write a test case? I cannot see parameter binding in your example (specifically, query and parameter format)
|
This "fixes" doctrine/orm#7827, by actually passing the correct type as parameter. And the "type hint" can be removed, as well.
This "fixes" doctrine/orm#7827, by actually passing the correct type as parameter. And the "type hint" can be removed, as well.
This "fixes" doctrine/orm#7827, by actually passing the correct type as parameter. And the "type hint" can be removed, as well.
BC Break Report
Summary
Upgrading from 2.6.3 to 2.6.4 triggers an error related to obejct parameters in queries.
Previous behavior
It worked ;)
Current behavior
How to reproduce
Update
doctrine/orm
from 2.6.3 to 2.6.4 and see it fail. The code is complex, but the main part involved should be:My wild guess would that the fix #7527 in PR #7528 might cause it.
The text was updated successfully, but these errors were encountered: