Support the continueAfterTimeout parameter #30
Merged
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.
Implements support for the continueAfterTimeout parameter mentioned in #29 by adding a new optional argument to the aurora_data_api.connect() function called
continue_after_timeout
. This argument is passed to theAuroraDataAPIClient
andAuroraDataAPICursor
and is used inside the cursor to add an additionalexecute_arg
.The corresponding unit test is skipped if an environment variable
TEST_CONTINUE_AFTER_TIMEOUT
is notTrue
(it is consideredFalse
if it does not exist) to make it an opt-in test. The unit test is also skipped ifusing_mysql
because the implementation uses thepg_sleep()
function that does not exist in MySQL. An implementation of this test for MySQL could be added. I could not add it because I do not have an Aurora MySQL DB that I can access easily.