ppooled-pg

ppooled-pg
==========

> Promisified PostgreSQL driver with more effective pooling strategies.

Brief
-----

This is simply a personal promise wrapper for wonderful but non promise aware
PostgreSQL driver pooled-pg.

This is not intended, at least nowadays, to be a complete full-featured tool.
This only has methods I found handy for my own purposes.

But push requests are welcome if anyone is interested in improving it.

Índex
-----

* Setup
* Usage
* Instantiation
* Promisified methods
* query(sql, args)
* queryRows(sql, args)
* Synchronous methods
* querySync(sql, args):
* queryRowsSync(sql, args):
* Advanced Features
Support for SQL Tagged Templates*
arguments* Symbol
* Contributing

Setup
-----

``sh
npm install ppooled-pg
`


Usage
-----

$3

`javascript

var pPooled = require("ppooled-pg");

var ppg = pPooled({
protocol: "postgresql", // "postgresql" (default) or "remote".
// See https://www.npmjs.com/package/pooled-pg#advanced-usage-remote-mode
user: "db_user_name",
password: "db_user_password",
connect: "db_user_connect_string",
// See pooled-pg documenetation for more details on connect string:
// https://www.npmjs.com/package/pooled-pg
});

`

$3


#### query(sql, args)

Simple wrapper to pooled-pg query method.

`javascript
var q = ppg.query(sql, args);

q.then(function(result){
console.log(result);
// result.rows = Actual result data.
}.catch(function(err){
console.error(err);
// Some error happened.
});
`


#### queryRows(sql, args)

Like query() but strip out all metadata retuning just resulting rows (more
handy if you don't care about other stuff).

`javascript
var q = ppg.queryRows(sql, args);

q.then(function(result){
console.log(result);
// result = Actual result data.
}.catch(function(err){
console.error(err);
// Some error happened.
});
`

$3

Synchronous methods works just the same as its promisified counterparts (in
fact they are just wrappers over them) but returns data syncronously instead of
as promise.

>
It may seem weird having synchronous methods in a promise library. But
sometimes is Ok to read some data synchronously. Specially at startup, when is
so common having to read common parameters that are needed for almost all the
rest of the process.
>
Having synchronous methods saves us to be forced to install another PostgresSQL
library to do just that and, most importantly, dealing with different syntax
and / or outcome formatting.
>

$3

`javascript
try {
console.log(ppg.querySync(sql, args));
} catch (err) {
console.error(err);
// Some error happened.
};
`

$3

`javascript
try {
console.log(ppg.queryRowsSync(sql, args));
} catch (err) {
console.error(err);
// Some error happened.
};
`

Advanced Features
-----------------

$3

SQL Tagged Templates (SQLTT) version
0.0.2 or higher are supported from ppooled-pg 0.3.0.

That means we can pass an SQLTT instance instead of actual SQL string.

In this case, proper PostgreSQL version of its SQL will be picked up and
parameters will be parsed through its args() method.

$3

>
WARNING: This feature was introduced before SQL Tagged
Templates and is mantained due to backward
compatibility reasons. But it could be removed in future versions (in which
case major version number would be increased too).
>

Passing arguments as an array can be awkward sometimes. Specially if you have a
lot of them.

JSON objects are much more handy, but most SQL engines only accept arguments as
positional parameters.

ppooled-pg takes advantadge of ES6+ wonderful Symbol feature to allow
providing SQL as a String object with optional "arguments" symbol for that.

Example:
`
const $args$ = Symbol.for("arguments");

const sql = new String(
select foo from bar
where baz = $1
and foobar = $2
);

sql[$args$] = ["baz", "foobar"];

ppg.queryRows(sql, {
foobar: "foobar value",
baz: "baz value"
}).then(data=>console.log(data));

``

>
Also, not provided values are silently replaced by nulls as well so, for
inserts and updates, there is no need to pass all parameters if they aren't
declared as 'NOT NULL' or have a default value.
>

Contributing
------------

If you are interested in contributing with this project, you can do it in many ways:

* Creating and/or mantainig documentation.

* Implementing new features or improving code implementation.

* Reporting bugs and/or fixing it.

* Sending me any other feedback.

* Whatever you like...

Please, contact-me, open issues or send pull-requests thought this project GIT repository