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

mysql-deploy-redux

v0.1.2

Published

Deploys your schema changes and routines, it versions all your changes and roles back failed routines to previous versions

Downloads

3

Readme

mysql-deploy


This useful little package takes the pain out of updating keeping your database up to date, whether in the development environent or production.

Installation

sudo npm install mysql-deploy --save

Usage

Call scriptDeploy method at the end of your main script before your app finishes starting. In an ExpressJS app I place the app.listen() inside the callback function so my server won't start untill all the scripts have deployed.

var scriptDeploy = require('mysql-deploy ');

var options = {
    host 				: 'example_host',
	port				: 33306,
    user 				: 'username',
    password 			: 'password',
    database 			: 'example_database',
    schemaLocation		: path.join(__dirname, 'databaseScripts', 'schemaScripts'), 
    routinesLocation	: path.join(__dirname, 'databaseScripts', 'routineScripts') 
};

scriptDeploy(options, function(err) {
	if (err) throw err;
	app.listen(3000);
});

Schema scripts

All schema scripts should be placed in the folder specified by the schemaLocation option.

  • All script files should begin with the version number followed by a descriptive name.
  • Script files can contain multiple statements
  • If a script file fails to run correct the script and restart your application ( you may have to wait for two minutes for scirpt-deploy to unlock)
  • Once a script has successfully run it will not run again, even if the file is changed.

Routines

All routines should be places in the folder specified by the routinesLocation option.

  • Name your routine script files the same as the routines themselves (this is not a requirement, just advice really)
  • To change a routine simply modify the file. Next time your node application starts it will know the routine has changed, drop and recreate it.
  • Currently stored procedures and functions will both work.
  • Do not use the DELIMETER syntax in your routines, it is not only unnecessary but will cause the scripts to fail.

Example syntax for function script

CREATE FUNCTION SqrRt (x1 decimal, y1 decimal)
RETURNS decimal
DETERMINISTIC
BEGIN
  DECLARE dist decimal;
  SET dist = SQRT(x1 - y1);
  RETURN dist;
END

Options

  • host: The database host name/IP address for the MySql database server you wish to connect to.
  • user : The database username you wish to use to connect to the database. This user must have all the rights that your stored procdures and functions require aswell as the rights to perform the functions in the schema scripts.
  • password: The database password for the above user.
  • database: The name of the database that you wish to run all the scripts on.
  • schemaLocation: The folder location of the schema change scripts, this should be an absolute path.
  • routinesLocation: The folder location of the schema change scripts, this should be an absolute path.

Create database

If the database name in the database options does not exist, mysql-deploy will attempt to create it. If it fails for any reason, lack of permissions or incorrect connection details, it will halt and no futher scripts will run.

mysql-deploy management tables

mysql-deploy creates 3 tables the first time you run it in an app. These table will live on the database named in the database option. They are used to track the versions of the schema scripts, functions and stored procedures. It is best to avoid modifying or manually adding any data in these tables.

These tables are:

  • database_update_lock
  • database_script_history
  • database_routine_history

Locking

When running, mysql-deploy locks itself to prevent other instances of mysql-deploy from running at the same time. This lock only lasts for two minutes so please be patient.