Automatically select 'cursor' protocol for redshift-prefixed connection strings #187
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
…ed connection strings (in all other cases default to 'binary', as before)
|
Hi @alexander-beedie , thanks for the PR! I have merge it and it will be in our next release (0.2.3). I'm also going to make an alpha release now so you can use it earlier. Will let you know once it's done. |
|
@alexander-beedie the alpha version |
Thanks - just tested; works like a charm... ;) |
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.
A small backwards-compatible patch (no behaviour changes to any existing calls), that allows redshift-prefixed connection strings to select the correct protocol ("cursor") automatically, and proceed as if postgres. All other connections default to "binary", as before.