-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Feature: support for LISTEN/NOTIFY? #23
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
Comments
All features, including this one, work both with the native libpq bindings and the pure javascript flavor of node-postgres. I realize this could be better documented. I'll leave this open until I put this information up on the wiki. |
Awesome, time for me to do some homework on this then. Thanks! |
I updated the wiki with documentation (it's near the bottom) |
brianc
pushed a commit
that referenced
this issue
Dec 27, 2019
* Support function-like construction Remove the necessity of using `new` in front of the `Pool`, i.e. allow it to be used as a regular function. This is following #1077 * add Pool factory test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe node-postgres already supports the LISTEN/NOTIFY features of postgres in which case I apologize! If not I think this would be an interesting addition which would make a lot of sense in nodejs since it's so call-back focused!
node-PostgresClient has support for this it looks like but node-postgres looks more active.
The text was updated successfully, but these errors were encountered: