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-autopatch

v0.1.1

Published

Node application for automatically applying postgreSQL database patches.

Downloads

4

Readme

#node-postgres-autopatch

Node application for automatically applying postgreSQL database patches.

#Features

  • Automatic database patch application
  • SQL patches
  • Javascript patches

#Installation

npm install pg-autopatch

#Examples

var path = require('path');
var autopatch = require('pg-autopatch');

var config = {
	patchDir: path.resolve(__dirname, './patches/'),
	dbType: 'postgres',
	db: {
		host: 'localhost',
		port: 5432,
		user: 'postgres',
		database: 'db_name',
		password: 'password',
		patchTableName: 'patches'
	}
};

autopatch.run(config, function(err, newPatchesApplied) {
	console.log('autopatch done. %d new patches applied', newPatchesApplied);
});

#Notes

postgres-autopatch will create a table in the specified database called 'db_patch', in order to keep track of the applied patches. It will look in the patch directory specified in the config object for new patches to apply. New patches should be placed in this directory and postgres-autopatch will apply them when the autopatcher's run method is called. run should be called on application startup, so that it finishes before any server logic is executed. Patches should have names following the pattern db_001_patch_name.sql or db_002_patch_name.js.

##SQL Patches

An SQL patch file can be any valid SQL file. Every statement in the patch file will be executed in sequence.

##Javascript Patches

postgres-autopatch also supports javascript patch files, where more complex patches can be applied with logic. Javascript patch files must adhere to a specific format in order for them to be applied correctly. For Example:

var pg = require('pg');

module.exports = function(dbConfig, callback) {

	pg.connect(dbConfig, function(err, client, done) {
		var sql = "SELECT * FROM test_table";
		
		client.query(sql, function(err, response) {
			console.log(response);
			done();
		});
	});
};

You must use require('pg') in the patch file and export a function with a dbConfig and callback parameter. You may then use the dbConfig object to connect to the database and query using whatever logic you want.