status-im/migrate
2
0
Fork 0
mirror of https://github.com/status-im/migrate.git synced 2025-02-23 00:08:06 +00:00
Code Issues Projects Releases Wiki Activity

Use reverse/down migration instead of rollback

Browse Source
This commit is contained in:
Marcin K 2019-08-07 22:01:04 +02:00
parent e98f9f6a24
commit 44b07c5f7b
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
TUTORIAL.md
View File

@ -1,5 +1,5 @@
# Getting started # Getting started
Before you start, make sure you understand the concept or database migration and rollback. Before you start, you should understand the concept of forward/up and reverse/down database migrations.
Create new Go project and configure a database for it. Make sure that your database is supported [here](README.md#databases) Create new Go project and configure a database for it. Make sure that your database is supported [here](README.md#databases)
For the purpose of this tutorial let's create PostgreSQL database called `example`. For the purpose of this tutorial let's create PostgreSQL database called `example`.
@ -53,14 +53,14 @@ Indexes:
"users_email_key" UNIQUE CONSTRAINT, btree (email) "users_email_key" UNIQUE CONSTRAINT, btree (email)
"users_username_key" UNIQUE CONSTRAINT, btree (username) "users_username_key" UNIQUE CONSTRAINT, btree (username)
``` ```
Great! Now let's check if rollback also works: Great! Now let's check if running reverse migration also works:
``` ```
migrate -database ${POSTGRESQL_URL} -path db/migrations down migrate -database ${POSTGRESQL_URL} -path db/migrations down
``` ```
Make sure to check if your database changed as expected on rollback. Make sure to check if your database changed as expected in this case as well.
**Before commiting your migrations:** You should run your migrations, rollback them, and then run them again to see if migrations are working properly both ways. **Before commiting your migrations:** You should run your migrations up, down, and then up again to see if migrations are working properly both ways.
(e.g. if you created a table in a migration but rollback did not delete it, you will encounter an error when running the migration again) (e.g. if you created a table in a migration but reverse migration did not delete it, you will encounter an error when running the forward migration again)
It's also worth checking your migrations in a separate, containerized environment. You can find some tools in the end of this tutorial. It's also worth checking your migrations in a separate, containerized environment. You can find some tools in the end of this tutorial.
**Hint:** Most probably you are going to use to the above commands often, it's worth putting them in a Makefile of your project. **Hint:** Most probably you are going to use to the above commands often, it's worth putting them in a Makefile of your project.