From 26f17d5141fbf0bf6dc85d7d9e6a9bca6841bea7 Mon Sep 17 00:00:00 2001 From: Adrian Macneil Date: Thu, 24 Sep 2020 10:14:31 -0700 Subject: [PATCH] Document migration order (#160) --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 92a7396..34d133d 100644 --- a/README.md +++ b/README.md @@ -205,6 +205,8 @@ Writing: ./db/schema.sql > Note: `dbmate up` will create the database if it does not already exist (assuming the current user has permission to create databases). If you want to run migrations without creating the database, run `dbmate migrate`. +Pending migrations are always applied in numerical order. However, dbmate does not prevent migrations from being applied out of order if they are committed independently (for example: if a developer has been working on a branch for a long time, and commits a migration which has a lower version number than other already-applied migrations, dbmate will simply apply the pending migration). See [#159](https://github.com/amacneil/dbmate/issues/159) for a more detailed explanation. + ### Rolling Back Migrations By default, dbmate doesn't know how to roll back a migration. In development, it's often useful to be able to revert your database to a previous state. To accomplish this, implement the `migrate:down` section: