You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time, @beberlei closed the PR for the following reason, deemed unfixable:
Passing a type into the parameters is not recognized during caching, that means, using a DQL cache, the same DQL statement with (different parameter types) will lead to the same SQL being generated, depending on if the first or the second set parameter query is executed first.
This PR re-integrates the original fix, and offers a solution to the above issue: take the parameter types into account when checking the local ParserResult and the query cache.
In addition to the test for the DDC-2224 issue, I added a test to ensure that changing a parameter type invalidates the cache.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of BenMorel:
Url: #1339
Message:
This is a follow-up to the abandoned #574 by @mnapoli, that fixes [DDC-2224](http://www.doctrine-project.org/jira/browse/[DDC-2224]%28http://www.doctrine-project.org/jira/browse/DDC-2224%29).
At the time, @beberlei closed the PR for the following reason, deemed unfixable:
This PR re-integrates the original fix, and offers a solution to the above issue: take the parameter types into account when checking the local
ParserResult
and the query cache.In addition to the test for the DDC-2224 issue, I added a test to ensure that changing a parameter type invalidates the cache.
The text was updated successfully, but these errors were encountered: