317 bigquery using dbi#328
Open
javier-gracia-tabuenca-tuni wants to merge 9 commits intoOHDSI:developfrom
Open
317 bigquery using dbi#328javier-gracia-tabuenca-tuni wants to merge 9 commits intoOHDSI:developfrom
javier-gracia-tabuenca-tuni wants to merge 9 commits intoOHDSI:developfrom
Conversation
…s delayIfNecessaryForDdl and delayIfNecessaryForInsert, just like it does for JDBC
… tests/testthat/setup.R
Author
|
this PR is for #317 Changes:
Minor Changes:
Doubts I got when applying the tests. Not sure If changing the test is the correct path:
Still TO DO Im not sure what would be the best way to modify the DatabaseConnector:::connectBigQuery function I can work on that if you believe this is going correctly |
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
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.
Before you do a pull request, you should always file an issue and make sure the package maintainer agrees that it’s a problem, and is happy with your basic proposal for fixing it. We don’t want you to spend a bunch of time on something that we don’t think is a good idea.
Additional requirements for pull requests:
Adhere to the Developer Guidelines as well as the OHDSI Code Style.
If possible, add unit tests for new functionality you add.
Restrict your pull request to solving the issue at hand. Do not try to 'improve' parts of the code that are not related to the issue. If you feel other parts of the code need better organization, create a separate issue for that.
Make sure you pass R check without errors and warnings before submitting.
Always target the
developbranch, and make sure you are up-to-date with the develop branch.