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

Treat undefined values as NULL #56

Merged
merged 1 commit into from
Oct 20, 2011
Merged

Treat undefined values as NULL #56

merged 1 commit into from
Oct 20, 2011

Conversation

bdunavant
Copy link
Contributor

I believe this is good?

Also, two things I ran into while testing.

  1. I think script/create-test-tables.js needs var sys = require('utils'); to be ../lib/utils

However, this could just be an issue on my side with pathing or something so I didn't want to put it in the pull request.

  1. I had to npm install generic-pool in order to make test with the master branch. I do NOT have to do that with the version of node-postgres on npm currently. I'm assuming this is something new that isn't part of what is published on npm.

@brianc brianc merged commit 94dc7fd into brianc:master Oct 20, 2011
brianc added a commit that referenced this pull request Dec 18, 2019
When code was added to use a random named portal instead of the empty portal to support redshift we didn't update the close messages approprately.  This could result in postgres keeping locks on tables for modification if streaming and table modification was both done within a transaction.  This update fixes the issue by always issuing a close command on the named portal when query is finished.

fixes #56
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.

2 participants