This repository was archived by the owner on Feb 2, 2024. It is now read-only.
Configure isolation level as a parameter. #25
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
It used to set the isolation level AUTOCOMMIT everywhere. This isolation level unfortunately is irrelavant for most databases. The isolation level is now optional, which means if not configured, the SQL engine will apply the default isolation of your backend database. You can now set the isolation level of your choice however when running a project. Also added a new parameter to CLI to reflect this new parameter.
Closed
|
@sp-enric-fradera @sp-joan-madrid pip uninstall sqlbucket
pip install sqlbucket==0.3.3.dev3You can run a small ETL, with a step failing on purpose and check that previous steps were actually committed. I've tested it in local and it worked but I just want to be sure I'm not initiating a breaking change on your system. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It used to set the isolation level AUTOCOMMIT everywhere. This isolation level unfortunately is irrelevant for most databases.
The isolation level is now optional, which means if not configured, the SQL engine will apply the default isolation of your backend database. You can now set the isolation level of your choice however when running a project. Also added a new parameter to CLI to reflect this new parameter.