Migrations are used to build and modify your database tables. This is done through use of migration files and the
Schema class. Migration files are really just wrappers around the
Schema class as well as a way for Masonite to manage which migrations have run and which ones have not.
Creating migrations are easy with the migration commands. To create one simply run:
$ masonite-orm migration migration_for_users_table
This will create a migration file for you and put it in the
If you want to create a starter migration, that is a migration with some boilerplate of what you are planning to do, you can use the
$ masonite-orm migration migration_for_users_table --create users
This will setup a migration for you with some boiler plate on creating a new table
$ masonite-orm migration migration_for_users_table --table users
This will setup a migration for you for boiler plate on modifying an existing table.
To start building up your migration, simply modify the
up method and start adding any of the available methods below to your migration.
A simple example would look like this for a new table:
class MigrationForUsersTable(Migration):def up(self):"""Run the migrations."""with self.schema.create("users") as table:table.increments('id')table.string('username')table.string('email').unique()table.string('password')table.boolean('is_admin')table.integer('age')table.timestamps()def down(self):"""Revert the migrations."""self.schema.drop("users")
The varchar version of the table. Can optional pass in a length
The INT version of the database. Can also specify a length
The auto incrementing version of the table. An unsigned non nullable auto incrementing integer.
An unsigned non nullable auto incrementing big integer. Use this if you expect the rows in a table to be very large
BINARY equivalent column. Sometimes is text field on unsupported databases.
BOOLEAN equivalent column.
CHAR equivalent column.
JSON equivalent column.
DATE equivalent column.
YEAR equivalent column.
DATETIME equivalent column.
TIMESTAMP equivalent column.
TIME equivalent column.
DECIMAL equivalent column. Can also specify the length and decimal position.
DOUBLE equivalent column. Can also specify a float length
ENUM equivalent column. You can also specify available options as a list.
TEXT equivalent column.
UNSIGNED INT equivalent column.
TINY INT equivalent column.
SMALL INT equivalent column.
MEDIUM INT equivalent column.
BIG INT equivalent column.
TINY auto incrementing equivalent column.
A nullable DATETIME column named
In addition to building up the migration, you should also build onto the
down method which should reverse whatever was done in the
up method. If you create a table in the up method, you should drop the table in the down method.
DROP TABLE equivalent statement.
DROP TABLE IF EXISTS equivalent statement.
DROP COLUMN equivalent statement. Can take one or multiple column names.
Drops the constraint. Must pass in the name of the constraint.
Drops the uniqueness constraint. Must pass in the name of the constraint.
Drops the foreign key. Must specify the index name.
Renames a column to a new column. Must take the old column name, new column and data type.
Drops the primary key constraint. Must pass in the constraint name
At any time you can get the migrations that have run or need to be ran:
$ masonite-orm migrate:status
If you would like to see just the SQL that would run instead of running the actual migrations, you can specify the
-s flag (short for
--show). This works on the migrate and migrate:rollback commands.
python craft migrate -s
Refreshing a database is simply rolling back all migrations and then migrating again. This "refreshes" your database.
You can refresh by running the command:
$ masonite-orm migrate:refresh
In addition to the available columns you can use, you can also specify some modifers which will change the behavior of the column:
Allows NULL values to be inserted into the column.
Forces all values in the column to be unique.
Adds the column after another column in the table. Can be used like
Makes the column unsigned. Used with the
Makes the column use the
Specify a default value for the column. Can be used like table.boolean("is_admin").default(False)
In addition to columns, you can also create indexes. Below are the available indexes you can create:
Make the column use the PRIMARY KEY modifer.
Makes a unique index. Can pass in a column
Creates an index on the column.
Creates an fulltext index on the column or columns.
The default primary key is often set to an auto-incrementing integer, but you can use UUID instead.
If you want to create a foreign key you can do so simply as well:
And optionally specify an
You can use these options:
Sets the ON UPDATE SET NULL property on the constraint.
Sets the ON UPDATE CASCADE property on the constraint.
Sets the ON DELETE SET NULL property on the constraint.
Sets the ON DELETE CASCADE property on the constraint.
If you would like to change a column you should simply specify the new column and then specify a
.change() method on it.
Here is an example of changing an email field to a nullable field:
class MigrationForUsersTable(Migration):def up(self):"""Run the migrations."""with self.schema.table("users") as table:table.string('email').nullable().change()with self.schema.table("users") as table:table.string('email').unique()def down(self):"""Revert the migrations."""pass
You can truncate a table:
You can also temporarily disable foreign key checks and truncate a table:
You can drop a table:
You can drop a table if it exists: