Generate, execute, and roll back SQL migrations.
Want to see pretty graphs? Log in now!
npm install voltron-migrator
|4||downloads in the last week|
|13||downloads in the last month|
|Last Published By|
|Version||0.7.4 last updated 6 months ago|
|Keywords||database, voltron.io, migration, sql, postgres, mysql|
|Dependencies||optimist, moment, q|
Voltron-Migrator is a tool for executing SQL migrations with Node. While it's part of the Voltron.io framework, it's also a stand-alone component. Voltron-Migrator is heavily modeled after voodootikigod's migrator; in fact, the project started as a fork of voodootikigod's code.
Voltron-Migrator has two main purposes: generate SQL migrations, and execute them.
V-M allows both the application and reversion of migrations. Like Rails,
it creates a
schema_migrations table in your database to track which
migrations have already been executed, and it prefixes generated
migration files with a timestamp of 'YYYYMMDDHHMMSS'.
Migrations are written in SQL and do not use an abstraction layer.
Include Voltron.io or Voltron-Migration in your package.json file. If you
node_modules\.bin in your path, just execute
migrate. You can
provide database configuration in two ways:
via a configuration file that will be required. The config file must return an object with a
databaseproperty, which itself exposes a hash of the following properties: name, host, port, type, user (optional), password (optional).
via explicit values on the command line. The following properties are required: name, host, port, type. User and password are optional.
V-M assumes that your migrations are included in
.\migrations, but you
can change that via a CLI argument.
migrate on its own will execute migrations in order in the specified
source directory, skipping over migrations that have already been run. If
--revert as an argument, the migrations were be rolled back,
starting with the most recent migration and ignoring any migrations that
haven't yet been applied.
migrate -g or
<filename> will create two
migration files of the specified filename:
<filename>_down.sql. As you can expect,
up files are run when migrations
are executed, and
down files are run when migrations are reverted.
Postgres is currently supported.
- Add test coverage
- Implement MySQL
- Allow reversion by datestamp
In order to run the tests, you'll need to setup a database for Postgres
migrator_test). See the config files in
test/fixtures for details.
The MIT License (MIT) Copyright © 2012-3 Justin Reidy, http://rzrsharp.net
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.