npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-postgres-named

v2.4.1

Published

Named parameters for node-postgres.

Downloads

10,012

Readme

node-postgres-named

Named parameters for node-postgres.

Circle CI npm version dependencies

Why node-postgres-named?

Want to use postgres with node? node-postgres has you covered. Want named parameters?

Well, postgres itself doesn't support them, and brianc has sagely opted to keep his library small and close to the postgres specification.

But SQL replete with meaningless numeric tokens (e.g. $1) isn't very readable. This module lets you monkeypatch node-postgres or node-postgres-pure to support named parameters.

Go from this...


client.query('SELECT name FROM person WHERE name = $1 AND tenure <= $2 AND age <= $3',
             ['Ursus', 2.5, 24],
             function (results) { console.log(results); });
             

to this...


client.query('SELECT name FROM person WHERE name = $name AND tenure <= $tenure AND age <= $age',
             {'name': 'Ursus', 'tenure': 2.5, 'age': 24},
             function (results) { console.log(results); });
     

Tokens are identified with \$[a-zA-Z]([a-zA-Z0-9_\-]*)\b. In other words: they must begin with a letter, and can contain only alphanumerics, underscores, and dashes.

Execution of prepared statements is also supported:

client.query({
  name   : 'select.person.byNameTenureAge',
  text   : "SELECT name FORM person WHERE name = $name AND tenure <= $tenure AND age <= $age",
  values : { 'name': 'Ursus Oestergardii',
             'tenure': 3,
             'age': 24 }
}, function (results) { console.log(results); });

Usage

Create a client as usual, then call the patch function on it. It will be patched in-place.

var pg = require('pg'); 
var named = require('node-postgres-named');
var client = new pg.Client(conString);
named.patch(client);

Now both of the above call styles (with a list of values, or a dictionary of named parameters) will work.

Contributors

Inspiration provided by a conversation with Mike "ApeChimp" Atkins. Support for prepared statements added by nuarhu. Critical connection-pooling bugfix tediously diagnosed and patched by Tony "tone81" Nguyen. Mike "mfine15" Fine righted my unaesthetic mixing of double and single-quotes, and Victor Quinn fixed a spelling error.