Utility to migrate an SQLite 3 database using basic tools available in *NIX systems. It uses bash and sqlite3 commandline tool.
redstart OPTIONS COMMAND
OPTIONS
--db-file <PathToDbFile>
SQLite database file to work on.
--migrations-dir <Directory> [default: current-working-directory]
Directory where the migration SQL files are kept.
--base-db-file <PathToBaseDbFile> [optional]
The base SQLite database file to apply migrations to, in order to create
the database file (specified by --db-file)
COMMAND
migrate-to <MigrationID> OR "latest"
Migrate the database file specified in --db-file to the specified MigrationID.
If the db-file does not exist, it will be either copied from base-db-file, if
specified, or a new one is created. If no migration table (_Migration)
exists, it will be created and populated with details of migrations found in
migrations-dir.
If the argument given is "latest", then the latest MigrationID is figured out
and applied.
list-migrations
List current migrations and their status (whether applied or not).
check
Check if there are any migrations to be applied. If there are any pending
migrations the exit code is set to 1 otherwise 0.
You need gitman to install bash-pack which is required for redstart to work.
# clone and cd into the redstart
git clone https://github.com/codemedic/redstart.git
# run gitman to install dependencies
docker run --rm -it --volume="$(pwd)/redstart:/project" redmatter/gitman install
An alternative to above instructions would be to use a docker image. You can either build it locally or make use of the docker image codemedic/redstart.
docker run --rm -it
-v "${PWD}:/project" \
codemedic/redstart \
--db-file /project/data.db3 \
--migrations-dir /project/schema \
--base-db-file /project/schema/base.db3 \
<COMMAND>
For a project with directory structure as below. The optional --base-db-file option specifies base.db3, which contains tables before any changes were managed with redstart.
project
|-- data.db3
`-- schema
|-- 1_down_add-products-table.sql
|-- 1_up_add-products-table.sql
|-- 2_down_add-orders-table.sql
|-- 2_up_add-orders-table.sql
`-- base.db3
You can start off by creating empty files for both UP and DOWN migrations, as below. When you choose a MigrationID, make sure it is not a duplicate of any of the already existing migrations.
touch <migration-dir>/<NewID>_{up,down}_<ShortDescription>.sql
The ShortDescription cannot contain spaces or dots. See example below.
touch ./$(date +%Y%m%d)_{up,down}_create-group-table.sql
When adding SQLs to these migration files, it will be a good idea to wrap them in transactions. It will make sure that the database is left in a sane state, if the migration fails for what ever reason.
If there ever be a need to "ditch" a migration that is already known to the database, then manual intervention will be required.
The migration will have to be removed from _Migrations table, before adding any more migrations. If you require further assistance with this, feel free to log an issue.
Redstarts are a species of small, migratory birds; taking inspiration from the feather on SQLite logo.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent