Fixing issue when number of positional parameters != number of given types #301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guilhermeblanco
added a commit
that referenced
this pull request
Apr 8, 2013
…aults Fixing issue when number of positional parameters != number of given types
|
I had to revert this merge, because of http://www.doctrine-project.org/jira/browse/DBAL-496 |
Merged
beberlei
pushed a commit
that referenced
this pull request
May 9, 2013
This was referenced Dec 6, 2015
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When passing incomplete type information to
Connection::query(),SQLParserUtilscurrently behaves the wrong way as it ignores all typing information instead falling back to a default (PDO::PARAM_STR). I don’t know this place very well, so please review carefully.