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

pgprom

v1.0.1

Published

Easiest and safest way to use postgres abusing template strings

Downloads

1

Readme

pgprom

Easiest and safest way to use postgres abusing template strings

This is a tiny library that uses pg under the hood. The aim of this library is to create the easiest and safest way to run queries abusing the new template strings available in ES2015. Template strings can be tagged and the tagging function is responsible of concatenating the raw portions of the string with the interpolated values and it can also return anything, not only strings. pgprom uses these two capabilities to:

  • Automatically build a SQL with all the interpolated values replaced with placeholders and thus avoiding any SQL injection
  • Return a promise that will contain the query result

Installing

npm install pgprom --save

Usage

Instantiating

const sql = require('pgprom')(process.env.DATABASE_URL)

query()

This method returns all the information provided by pg when running SQL.

const status = 'open'
const interval = '1 year'
sql.query`SELECT * FROM issues WHERE status=${status} AND created_at > NOW() interval ${interval}`
  .then((result) => {
    console.log('rows', result.rows)
    console.log('rowCount', result.rowCount)
    // etc.
  })

find()

This method is like .query() but it only returns the array of rows.

const status = 'open'
const interval = '1 year'
sql.find`SELECT * FROM issues WHERE status=${status} AND created_at > NOW() interval ${interval}`
  .then((rows) => {
    console.log('rows', rows)
  })

findOne()

This method is like .find() but it only returns the first returned row.

const status = 'open'
const interval = '1 year'
sql.findOne`SELECT * FROM issues WHERE status=${status} AND created_at > NOW() interval ${interval} ORDER BY created_at ASC LIMIT 1`
  .then((row) => {
    console.log('row', row)
  })

execute()

This method executes the SQL and returns the number of affected rows.

const date = ...
sql.execute`DELETE FROM issues WHERE created_at < ${date}`
  .then((rowCount) => {
    console.log('affected rows', rowCount)
  })

Dynamic queries

Interpolated values are perfecto for... values :) But if you want to create dynamic SQL queries there are things you don't want to escape. For example this doesn't work:

const func = something ? 'NOW' : 'VERSION'
sql.findOne`SELECT ${func}()`

This doesn't work because the function name will be escaped. So you need to use sql.raw() like this:

const func = something ? 'NOW' : 'VERSION'
sql.findOne`SELECT ${sql.raw(func)}()`

Now pgprom won't treat func as a value to be escaped. It will just concatenate the value to the rest of the SQL query.