fix: check for binds following variable naming convention #9
Conversation
This file contains hidden or 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
Signed-off-by: Guy-Robert Kernisant <grkernisant@gmail.com>
Member
| this repo is read only, please send patch to https://github.com/codeigniter4/CodeIgniter4 instead. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
The proposed change is to allow corner cases where $sql being passed
might already contain a DATETIME constraint that would be detected as a
named bind even though you could be wanting to do a simple bind.
Ex WHERE some_column = ? AND other_column = ?
(date_column IS NULL OR false_positive_1 LIKE '%05:48%' OR false_positive_2 LIKE '%05:48%')
Signed-off-by: Guy-Robert Kernisant grkernisant@gmail.com