Use query binding instead of interpolation - #72
Merged
Conversation
Contributor
Author
|
@josevalim i opened this just before the repo was archived and transferred, and I'd like to have this considered for merging. LMKWYT |
Member
|
Please rebase! Is this compatible with the dashboard? |
Contributor
Author
Yes, doesn't change any public API but I will triple check. |
Member
|
💚 💙 💜 💛 ❤️ |
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
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.
This patch switches the queries to using bind parameters instead of EEx interpolation.
This will make it safer to use these queries in applications like Phoenix LiveDashboard and also
utilize the arguments (which it currently doesn't).
There shouldn't be any user facing change to this patch, but should improve the security posture.