Execute postgres queries simply.
Run queries with node-postgres with less boilerplate. node-posgres is low level by design and rather verbose.
This is a simple abstraction I've spun into a module after implementing something like this in most of my projects.
npm install pg-query
var query = require'pg-query';query'SELECT NOW()'assertequalrows resultrows;;
Notice the callback is called with 3 parameters.
Next the rows returned by the query.
Finally the full result object which contains the same reference to the rows at
var query = require'pg-query';queryconnectionParameters = 'postgres://user:password@host:5432/database';//accepts optional array of values as 2nd parameter for parameterized queriesquery'SELECT $1::text as name' 'brian';
If a callback is not passed, a promise is returned that will be resolved with
var query = require'pg-query';queryconnectionParameters = 'postgres://user:password@host:5432/database';//accepts optional array of values as 2nd parameter for parameterized queriesvar promise = query'SELECT $1::text as name' 'brian';promisespreadonSuccess onError;
Often I find I'm getting a single row by ID.
query.first allows for easy composition into async structures by returning the first row of the query or null if there are no rows. Let me show you...
//this is the old way:varquery'SELECT * FROM "user" WHERE id = $1' idcberr rows ? rows0 : null//this is much easiervarqueryfirst'SELECT * FROM "user" WHERE id = $1' id cb//or even this if you're crazyvar getUserById = queryfirstbindquery 'SELECT * FROM "user" WHERE id = $1'
query.first does a bit of argument type checking. If you pass an array as the
values argument it is passed to the query unchanged. If you pass anything else truthy it is wrapped inside an array. This makes
query.first easier to compose and use.
pg-query is domain aware so your callback will always be called in the correct domain.
If you're not using domains it will gracefully ignore them.
pg-query uses whichever version of node-postgres you have installed in your project.
pg.defaults and/or environment variables to connect.
pg-query uses a random pooled database client for each query.
If you're using a transaction (eg
COMMIT) you need to check out a client from the pool manually.
Repeat: DO NOT USE THIS FOR RUNNING TRANSACTIONS
- Accept query object
- Accept anything that responds to
.toQuery(node-sql queries, etc)
- Possibly add some way to configure connection parameters