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
[DDC-2224] Honor convertToDatabaseValueSQL() in DQL query parameters #1339
Conversation
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-3625 We use Jira to track the state of pull requests and the versions they got |
@@ -250,7 +265,7 @@ private function _parse() | |||
return $this->_parserResult; | |||
} | |||
|
|||
$hash = $this->_getQueryCacheId(); | |||
$hash = $this->_getQueryCacheId($types); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency with the rest of the class, I'd say that _getQueryCacheId
directly accesses $this->_parsedTypes
instead, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I'll change this!
[DDC-2224] Honor convertToDatabaseValueSQL() in DQL query parameters
👍 |
1 similar comment
👍 |
Great, thanks for merging! It would be nice to change DDC-2224 from "invalid" to "fixed" also. Any chance this fix can land in the 2.5.0 release? |
@BenMorel this will land in |
@Ocramius 👍 Thanks! |
This is a follow-up to the abandoned #574 by @mnapoli, that fixes DDC-2224.
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.