-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
pg.connect is undocumented #1238
Comments
Yes, |
Yeah |
Thank you for the clarification.
I think it would be better to document it. A simple mention like " |
Can that future version be the next version? =) |
I prefer to have a single connection from the application's perspective. This is because I already use a connection pooler that is external from this perspective. It seems to me that using pg's built-in connection pooler would buy me nothing at the expense of introducing concepts that my application doesn't need. |
@pstef You would want |
I added this to the docs milestone so I'll include it as deprecated when I write them up. |
Question: What would then be the proper equivalent to the code shown at https://devcenter.heroku.com/articles/heroku-postgresql#connecting-in-node-js? |
|
👍 definitely good to close |
The
pg.connect
function is not mentioned in the README or the wiki. But the function exists and it's present in a lot of example code on the Internet.Is it deprecated? Is using
new pg.Pool()
preferred topg.connect
? Or are they both fully supported? Either way, it would be nice to have this function mentioned somewhere, so that people know which way to write their own code.The text was updated successfully, but these errors were encountered: