Skip to content
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

Multiple hosts support, try n2 #1987

Closed
wants to merge 4 commits into from
Closed

Multiple hosts support, try n2 #1987

wants to merge 4 commits into from

Conversation

qfox
Copy link

@qfox qfox commented Oct 5, 2019

Closes #1470

Copy link
Collaborator

@charmander charmander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This still just looks like parsing with no pure-JS-driver implementation?

"packet-reader": "1.0.0",
"pg-connection-string": "0.1.3",
"pg-native": "^3.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pg isn’t supposed to have a dependency on pg-native, since pg-native is optional.

@@ -20,16 +20,16 @@
"main": "./lib",
"dependencies": {
"buffer-writer": "2.0.0",
"connection-string": "^3.0.4",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

connection-string follows a different spec from libpq. I think a PostgreSQL driver should stick with the libpq format.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know.

@qfox
Copy link
Author

qfox commented Oct 7, 2019

Oh, not sure I can finish this in the near future. Sorry ;-(

Todo:

  • connection-string drop (or persuade to make a BREAKING change)
  • JS-version of server lookup with attributes target_session_attribute=read-write (analogue to libpq build-in)
  • drop pg-native dep

Still not sure what is actually right to do with connection-string. Fellows in pg-connection-string tells me to replace it with connection-string here, and here you saying we need to make it work with non-valid spec
Prob we should drop old behaviour because it disrespect modern URL/connstring specs

@charmander charmander closed this Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for multiple hosts
3 participants