Permalink
Browse files

fixed docs

  • Loading branch information...
1 parent 7560e47 commit 7b44767a88d349dca8d7de3f1ef2e50366c53786 @tj committed with kishorenc Dec 3, 2011
Showing with 10 additions and 10 deletions.
  1. +10 −10 Readme.md
View
@@ -76,22 +76,22 @@ The second creates `./migrations/001-add-owners.js`, which we can populate:
When first running the migrations, all will be executed in sequence.
- $ migrate
- up : migrations/000-add-pets.js
- up : migrations/001-add-jane.js
- up : migrations/002-add-owners.js
- up : migrations/003-coolest-pet.js
- migration : complete
+ $ migrate
+ up : migrations/000-add-pets.js
+ up : migrations/001-add-jane.js
+ up : migrations/002-add-owners.js
+ up : migrations/003-coolest-pet.js
+ migration : complete
Subsequent attempts will simply output "complete", as they have already been executed in this machine. `node-migrate` knows this because it stores the current state in `./migrations/.migrate` which is typically a file that SCMs like GIT should ignore.
- $ migrate
- migration : complete
+ $ migrate
+ migration : complete
If we were to create another migration using `migrate create`, and then execute migrations again, we would execute only those not previously executed:
- $ migrate
- up : migrates/004-coolest-owner.js
+ $ migrate
+ up : migrates/004-coolest-owner.js
You can also run migrations incrementally by specifying a migration.

0 comments on commit 7b44767

Please sign in to comment.