Add dateRange options to redcap_read functions #323
Merged
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
remove partial argument matching
Add dateRangeBegin and dateRangeEnd to redcap-read-oneshot-eav.R, redcap-read-oneshot.R, and R/redcap-read.R
|
@wibeasley, @ChemiKyle, noticed that you prefer snake_case to camelCase in your parameters. I am happy to make that change tonight if you like. |
wibeasley
added a commit
that referenced
this pull request
Mar 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add dateRangeBegin and dateRangeEnd to
redcap-read-oneshot-eav.R,redcap-read-oneshot.R, andredcap-read.R.This PR addresses Issue #321
Using this option with a recent
dateRangeBeginproduces a very fast query response. This option in the REDCap API subsets records returned by querying the redcap log event table for recent inserts and updates.Note a 20-30 tests failed on my machine before I started modifying this code. See Issue #322. I don't believe I added any more test failures.