54eb0fa216
Bumps [mocha](https://github.com/mochajs/mocha) and [@types/mocha](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/mocha). These dependencies needed to be updated together. Updates `mocha` from 3.4.2 to 10.5.2 - [Release notes](https://github.com/mochajs/mocha/releases) - [Changelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md) - [Commits](https://github.com/mochajs/mocha/compare/v3.4.2...v10.5.2) Updates `@types/mocha` from 5.2.7 to 10.0.7 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/mocha) --- updated-dependencies: - dependency-name: mocha dependency-type: direct:development update-type: version-update:semver-major - dependency-name: "@types/mocha" dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
pg-connection-string
Functions for dealing with a PostgresSQL connection string
parse method taken from node-postgres
Copyright (c) 2010-2014 Brian Carlson (brian.m.carlson@gmail.com)
MIT License
Usage
var parse = require('pg-connection-string').parse;
var config = parse('postgres://someuser:somepassword@somehost:381/somedatabase')
The resulting config contains a subset of the following properties:
user- User with which to authenticate to the serverpassword- Corresponding passwordhost- Postgres server hostname or, for UNIX domain sockets, the socket filenameport- port on which to connectdatabase- Database name within the serverclient_encoding- string encoding the client will usessl, either a boolean or an object with propertiesrejectUnauthorizedcertkeyca
- any other query parameters (for example,
application_name) are preserved intact.
Connection Strings
The short summary of acceptable URLs is:
socket:<path>?<query>- UNIX domain socketpostgres://<user>:<password>@<host>:<port>/<database>?<query>- TCP connection
But see below for more details.
UNIX Domain Sockets
When user and password are not given, the socket path follows socket:, as in socket:/var/run/pgsql.
This form can be shortened to just a path: /var/run/pgsql.
When user and password are given, they are included in the typical URL positions, with an empty host, as in socket://user:pass@/var/run/pgsql.
Query parameters follow a ? character, including the following special query parameters:
db=<database>- sets the database name (urlencoded)encoding=<encoding>- sets theclient_encodingproperty
TCP Connections
TCP connections to the Postgres server are indicated with pg: or postgres: schemes (in fact, any scheme but socket: is accepted).
If username and password are included, they should be urlencoded.
The database name, however, should not be urlencoded.
Query parameters follow a ? character, including the following special query parameters:
host=<host>- setshostproperty, overriding the URL's hostencoding=<encoding>- sets theclient_encodingpropertyssl=1,ssl=true,ssl=0,ssl=false- setssslto true or false, accordinglysslmode=<sslmode>sslmode=disable- setssslto falsesslmode=no-verify- setssslto{ rejectUnauthorized: false }sslmode=prefer,sslmode=require,sslmode=verify-ca,sslmode=verify-full- setssslto true
sslcert=<filename>- reads data from the given file and includes the result asssl.certsslkey=<filename>- reads data from the given file and includes the result asssl.keysslrootcert=<filename>- reads data from the given file and includes the result asssl.ca
A bare relative URL, such as salesdata, will indicate a database name while leaving other properties empty.