-
Notifications
You must be signed in to change notification settings - Fork 241
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
check for sql injection paths; switch to using prepared sql statements (dplyr?) #395
Labels
Comments
dlebauer
changed the title
check for sql injection paths
check for sql injection paths; switch to using prepared sql statements (dplyr?)
Apr 24, 2015
@robkooper status? |
removed milestone since this is a bigger issue that will need to be resolved slowly over time. |
@infotroph and I will probably try to tag-team this, as it's relevant for his Biocro work and my work on importing TRY. |
12 tasks
12 tasks
Merged
This issue is stale because it has been open 365 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pecan code base has lots of places where an sql injection can happen. We should switch as soon as possible to using prepared statements. We should look at the package dplyr for the database code (http://cran.rstudio.com/web/packages/dplyr/vignettes/databases.html). This package has two functions that might be hand escape and sql that will help create the queries.
dplyr has some other nice features in that you don't write sql statements but use functions to create select statements etc.
The text was updated successfully, but these errors were encountered: