-
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.19.7 breaks entity parameters when set from query-builder to native-query #11594
Comments
We have a native query ( We then transfer original QB parameters to the native one;
I believe it's incompatible API, but im not sure about the related commit here. |
Try reverting the one in my link please. |
Thanks! We're skipping |
The triggering call is |
It's unclear to me if you've tried reverting the commit or not. |
@greg0ire sorry! yes, commenting out
100% solves it. I dont think it should be part of a patch release. |
Of course, im also curious if we can maintain the current compatibility, since we rely on default infered typing. |
What is |
But after transfering from QB to native query, it becomes:
So we ignore typeSpecified when transfering, which is an implementation bug on our side. Unless it should be considered in |
possible userland patch: - $native->setParameter($index, $p->getValue(), $p->getType());
+ $native->setParameter($index, $p->getValue(), $p->typeWasSpecified() ? $p->getType() : null); |
BC Break Report
Summary
Given
(AbstractQuery) $qb->execute($qb->getParameters())
, if one of the parameters is a proxy entity, since 2.19.7 it produces:The text was updated successfully, but these errors were encountered: