Skip to content

Add client connectionString tests #1310

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

Merged
merged 3 commits into from
Jun 8, 2017
Merged

Conversation

brianc
Copy link
Owner

@brianc brianc commented Jun 8, 2017

Ensure connectionString is supported as a property on the client constructor config. This also allows pg-pool to pass a connection string via the connectionString config property & have it proxied to the client.

Documentation added here

brianc added 3 commits June 7, 2017 22:11
Add test to ensure { connectionString } is respected as an argument to the client constructor
Also fixed some legacy require statements.
@brianc brianc merged commit f2b87e0 into master Jun 8, 2017
@brianc brianc deleted the connection-string-property branch June 8, 2017 03:58
brianc added a commit that referenced this pull request Jun 9, 2017
* Add client connectionString tests (#1310)

* Remove redundant tests

* Add client connectionString test

Add test to ensure { connectionString } is respected as an argument to the client constructor

* Add test for connection string property

Also fixed some legacy require statements.

* Normalize native error properties

Map native error properties to the same property names we use for errors from the JS driver.

Fixes #972
Fixes #938
brianc added a commit that referenced this pull request Jun 9, 2017
* Add client connectionString tests (#1310)

* Remove redundant tests

* Add client connectionString test

Add test to ensure { connectionString } is respected as an argument to the client constructor

* Add test for connection string property

Also fixed some legacy require statements.

* Normalize native error properties

Map native error properties to the same property names we use for errors from the JS driver.

Fixes #972
Fixes #938
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.

1 participant