forked from brianc/node-postgres
-
Notifications
You must be signed in to change notification settings - Fork 0
Merge with upstream #6
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
Conversation
This file contains hidden or 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
defaults.js: fix typo in comment
Fixing error message misspelling.
Error message misspelling.
readme entry for pg-gen
Use connection configuration consistently in tests
doc update change username from jray to recursivefunk
Adding [pg-minify](https://github.com/vitaly-t/pg-minify) to the list of Extras.
Update README.md
…postgres Fix prepare value map to postgres
Adding MassiveJS to Extras section of README
pg-rxjs mention added
…issue brianc#934). Includes integration test.
Bring native API in line with pure js version. Fixes brianc#743
Support querying tables with column names with multiple apostrophes
Add pg-client to the list of extras in README.md
add option to parse input javascript Dates as UTC
I noticed that query cancellation was not working when connecting through pgbouncer, even though it worked fine when directly connected. This is because we're appending an extra null byte, and pgbouncer is strict about the packet length. (per http://www.postgresql.org/docs/9.1/static/protocol-message-formats.html) This removes the extraneous byte, which fixes cancellation against pgbouncer.
Fix byte representation of CancelRequest message
Move Extras section from README.md to Github wiki
readme: fix pool size
There was some nasty global-ish variable reference updating happening when the native module 'initializes' after its require with `require('pg').native` This fixes the issue by making sure both `require('pg')` and `require('pg').native` each initialize their own context in isolation and no weird global-ish references are used & subsequently stomped on.
…ixes Node.js v6.0.0 breakage. (brianc#1001)
* Change test matrix in .travis.yml Add tests for node @ v6. Remove node & postgres test permutations for older versions of node. * Remove sub-versions * Remove minor version from node 4
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.
No description provided.