-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Wiki: generic connection-string #1667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
Hi |
@azran4u Not yet, but I will ;) |
Thanks, i'll wait..
…On Mon, Jul 9, 2018, 18:47 Vitaly Tomilov ***@***.***> wrote:
@azran4u <https://github.com/azran4u> Not yet, but I will ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXXp2ypgDYLUG6vUEuo4b3dxq8fWaeZhks5uE3sYgaJpZM4UWzJV>
.
|
Support for multiple hosts has been implemented in version 0.6.0 of the library. So now |
Thanks for the update!
…On Fri, Jul 13, 2018, 19:40 Vitaly Tomilov ***@***.***> wrote:
Support for multiple hosts has been implemented in version 0.6.0 of the
library.
@azran4u <https://github.com/azran4u>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXXp2-fLYBTjq_HHAcztnfCmUTfHn8fTks5uGM2OgaJpZM4UWzJV>
.
|
This comment has been minimized.
This comment has been minimized.
Can we have this added, please? It was asked 1 year ago. |
Added. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please add connection-string to the list of extras, as a generic, fully optional syntax connection string parser and generator.
I intended to have it replace the current connection string, but found little support for doing so.
The project also has a separate branch to be released soon that will support the multi-host syntax that's needed here, in order to properly support PostgreSQL 10.0 and later.
The text was updated successfully, but these errors were encountered: