Brian M. Carlson
bf0c4bfaa9
Merge branch 'pull/326'
...
Conflicts:
lib/connection-parameters.js
test/unit/connection-parameters/creation-tests.js
2014-02-26 06:10:15 -06:00
Aurélio A. Heckert
c0fd4b1431
Set database on socket string connection
...
Allows to conect to a specific database trough this ways:
pg.connect('/some/path database', callback);
pg.connect('socket:/some/path?db=database', callback)
pg.connect('socket:/some/path?db=database&encoding=utf8', callback)
2013-12-19 15:37:26 -03:00
Brian Carlson
1674359b57
Respect SSL setting from connection parameters
2013-09-09 11:50:20 -05:00
brianc
bfdea752b2
Respect PGSSLMODE for setting SSL connection
2013-09-05 16:51:16 -05:00
Maciek Sakrejda
816e9b43ea
Use the standard postgres:// URL prefix for consistency
...
Fixes #286 .
2013-07-22 10:45:26 -07:00
Dave
f658b31aed
Changing to client_encoding, adding test for creating a connection
2013-06-06 12:16:36 -07:00
za-creature
264839d3a9
Update creation-tests.js
...
connection exports 'database' instead of 'path'
2013-04-11 23:10:43 +03:00
za-creature
20a2cbc810
Update creation-tests.js
...
added unittest for urlencoded components
2013-04-11 22:47:32 +03:00
Andrew Dunstan
ed015f9b58
Fix Unix domain socket setting.
...
This code was misconceived in that the host parameter for a Unix
domain socket connection must point to the directory containing
the socket, and not to the socket itself. Libpq will look for
the socket based on the host and port settings. See
<http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS >
2013-02-23 11:11:44 -05:00
bmc
6f73583112
add another test for weird connection strings
2013-01-29 20:06:50 -06:00
bmc
9dad56a54e
add more functionality to connection parameters
2013-01-21 15:44:55 -06:00
bmc
ec0d0beff2
build libpq connection string & support domain socket
2013-01-21 15:09:44 -06:00
bmc
868a9d0e8d
remove node-tap
2013-01-20 19:42:40 -06:00
bmc
92e75f0577
add ConnectionParameters object
2013-01-20 19:42:39 -06:00
