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

pg_error_parser

v1.0.1

Published

Micromodule for dealing with postgres errors

Downloads

5

Readme

pg_error_parser

A micro-module to make sense of error messages in postgresql. Works well with the pg module.

npm install pg_error_parser

Usage

format(error)

Takes an error object and adds more information to it. Useful when logging error objects and needing to see some normalized data.

Error lookups are based on the sqlState key of the error object.

Format will add the following keys to the error object:

code_name

Values such as not_null_violation, unique_violation, or invalid_sql_statement_name.

code_level

The severity of the error, either info, warning, or error.

code_group_name

A human readable name for this type of error like Integrity Constraint Violation, Invalid Transaction State, or Data Exception.

var pg = require('pg');
var pgep = require('pg_error_parser');
var client = new pg.Client();


client.query(text, params, function(err, result) {
  done();
  if (err) {
    err = pgep.format(err);
    // error object now has additional keys
    console.error(err);
    return callback(err);
  }
  callback(null, result);
});

getLevel(code)

Returns the error level of a given code.

getLevel('23505')
// error

getLevel('01P01')
// warn

getLevel('00000')
// info

getCodeName(code)

Returns the code name of a given code.

getLevel('23505')
// unique_violation

getLevel('01P01')
// deprecated_feature

getLevel('00000')
// successful_completion

getGroupName(code)

Returns the human readable name for and error if this type.

getLevel('23505')
// Integrity Constraint Violation

getLevel('01P01')
// Warning

getLevel('00000')
// Successful Completion

License

MIT