Database: Migrations

Migrations are like version control for your database, allowing your team to easily modify and share the application's database schema. Migrations are typically paired with Laravel's schema builder to easily build your application's database schema. If you have ever had to tell a teammate to manually add a column to their local database schema, you've faced the problem that database migrations solve.

The Laravel provides database agnostic support for creating and manipulating tables across all of Laravel's supported database systems.

Generating Migrations

To create a migration, use the make:migration Artisan command:

The new migration will be placed in your database/migrations directory. Each migration file name contains a timestamp which allows Laravel to determine the order of the migrations.

The —table and —create options may also be used to indicate the name of the table and whether the migration will be creating a new table. These options simply pre-fill the generated migration stub file with the specified table:

  1. php artisan make:migration create_users_table --create=users

If you would like to specify a custom output path for the generated migration, you may use the —path option when executing the make:migration command. The given path should be relative to your application's base path.

A migration class contains two methods: up and down. The up method is used to add new tables, columns, or indexes to your database, while the down method should simply reverse the operations performed by the up method.

Within both of these methods you may use the Laravel schema builder to expressively create and modify tables. To learn about all of the methods available on the Schema builder, check out its documentation. For example, this migration example creates a flights table:

  1. <?php
  3. use Illuminate\Support\Facades\Schema;
  4. use Illuminate\Database\Schema\Blueprint;
  5. use Illuminate\Database\Migrations\Migration;
  7. class CreateFlightsTable extends Migration
  8. {
  9.     /**
  10.      * Run the migrations.
  11.      *
  12.      * @return void
  13.      */
  14.     public function up()
  15.     {
  16.         Schema::create('flights', function (Blueprint $table) {
  17.             $table->increments('id');
  18.             $table->string('name');
  19.             $table->string('airline');
  20.             $table->timestamps();
  21.         });
  22.     }
  24.     /**
  25.      * Reverse the migrations.
  26.      *
  27.      * @return void
  28.      */
  29.     public function down()
  30.     {
  31.         Schema::drop('flights');
  32.     }
  33. }

Running Migrations

To run all of your outstanding migrations, execute the migrate Artisan command:

  1. php artisan migrate

Forcing Migrations To Run In Production

Some migration operations are destructive, which means they may cause you to lose data. In order to protect you from running these commands against your production database, you will be prompted for confirmation before the commands are executed. To force the commands to run without a prompt, use the —force flag:

  1. php artisan migrate --force

To rollback the latest migration operation, you may use the rollback command. This command rolls back the last "batch" of migrations, which may include multiple migration files:

  1. php artisan migrate:rollback

You may rollback a limited number of migrations by providing the step option to the rollback command. For example, the following command will rollback the last five migrations:

  1. php artisan migrate:rollback --step=5

The migrate:reset command will roll back all of your application's migrations:

  1. php artisan migrate:reset

Rollback & Migrate In Single Command

The migrate:refresh command will roll back all of your migrations and then execute the migrate command. This command effectively re-creates your entire database:

  1. php artisan migrate:refresh
  3. // Refresh the database and run all database seeds...
  4. php artisan migrate:refresh --seed

You may rollback & re-migrate a limited number of migrations by providing the step option to the refresh command. For example, the following command will rollback & re-migrate the last five migrations:

  1. php artisan migrate:refresh --step=5

Creating Tables

To create a new database table, use the create method on the Schema facade. The create method accepts two arguments. The first is the name of the table, while the second is a Closure which receives a Blueprint object that may be used to define the new table:

  1. Schema::create('users', function (Blueprint $table) {
  2.     $table->increments('id');
  3. });

Of course, when creating the table, you may use any of the schema builder's column methods to define the table's columns.

Checking For Table / Column Existence

You may easily check for the existence of a table or column using the and hasColumn methods:

Connection & Storage Engine

If you want to perform a schema operation on a database connection that is not your default connection, use the connection method:

  1.     $table->increments('id');
  2. });

You may use the engine property on the schema builder to define the table's storage engine:

  1. Schema::create('users', function (Blueprint $table) {
  2.     $table->engine = 'InnoDB';
  4.     $table->increments('id');
  5. });

Renaming / Dropping Tables

To rename an existing database table, use the rename method:

  1. Schema::rename($from, $to);

To drop an existing table, you may use the drop or dropIfExists methods:

  1. Schema::drop('users');
  3. Schema::dropIfExists('users');

Renaming Tables With Foreign Keys

Before renaming a table, you should verify that any foreign key constraints on the table have an explicit name in your migration files instead of letting Laravel assign a convention based name. Otherwise, the foreign key constraint name will refer to the old table name.

Columns

The table method on the Schema facade may be used to update existing tables. Like the create method, the table method accepts two arguments: the name of the table and a Closure that receives a Blueprint instance you may use to add columns to the table:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->string('email');
  3. });

Available Column Types

Of course, the schema builder contains a variety of column types that you may specify when building your tables:

Column Modifiers

In addition to the column types listed above, there are several column "modifiers" you may use while adding a column to a database table. For example, to make the column "nullable", you may use the nullable method:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->string('email')->nullable();
  3. });

Below is a list of all the available column modifiers. This list does not include the index modifiers:

Modifying Columns

Prerequisites

Before modifying a column, be sure to add the doctrine/dbal dependency to your composer.json file. The Doctrine DBAL library is used to determine the current state of the column and create the SQL queries needed to make the specified adjustments to the column:

  1. composer require doctrine/dbal

Updating Column Attributes

The change method allows you to modify some existing column types to a new type or modify the column's attributes. For example, you may wish to increase the size of a string column. To see the change method in action, let's increase the size of the name column from 25 to 50:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->string('name', 50)->change();
  3. });

We could also modify a column to be nullable:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->string('name', 50)->nullable()->change();
  3. });

Renaming Columns

To rename a column, you may use the renameColumn method on the Schema builder. Before renaming a column, be sure to add the doctrine/dbal dependency to your composer.json file:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->renameColumn('from', 'to');
  3. });

To drop a column, use the dropColumn method on the Schema builder. Before dropping columns from a SQLite database, you will need to add the doctrine/dbal dependency to your composer.json file and run the composer update command in your terminal to install the library:

You may drop multiple columns from a table by passing an array of column names to the dropColumn method:

  1. Schema::table('users', function (Blueprint $table) {
  2.     $table->dropColumn(['votes', 'avatar', 'location']);
  3. });

Creating Indexes

The schema builder supports several types of indexes. First, let's look at an example that specifies a column's values should be unique. To create the index, we can simply chain the unique method onto the column definition:

  1. $table->string('email')->unique();

Alternatively, you may create the index after defining the column. For example:

  1. $table->unique('email');

You may even pass an array of columns to an index method to create a compound index:

  1. $table->index(['account_id', 'created_at']);

Laravel will automatically generate a reasonable index name, but you may pass a second argument to the method to specify the name yourself:

  1. $table->index('email', 'my_index_name');

Available Index Types

Dropping Indexes

To drop an index, you must specify the index's name. By default, Laravel automatically assigns a reasonable name to the indexes. Simply concatenate the table name, the name of the indexed column, and the index type. Here are some examples:

If you pass an array of columns into a method that drops indexes, the conventional index name will be generated based on the table name, columns and key type:

  1. Schema::table('geo', function (Blueprint $table) {
  2.     $table->dropIndex(['state']); // Drops index 'geo_state_index'
  3. });

Laravel also provides support for creating foreign key constraints, which are used to force referential integrity at the database level. For example, let's define a user_id column on the posts table that references the id column on a users table:

  1. Schema::table('posts', function (Blueprint $table) {
  2.     $table->integer('user_id')->unsigned();
  4.     $table->foreign('user_id')->references('id')->on('users');
  5. });

You may also specify the desired action for the "on delete" and "on update" properties of the constraint:

  1. $table->foreign('user_id')
  2.       ->references('id')->on('users')
  3.       ->onDelete('cascade');

To drop a foreign key, you may use the dropForeign method. Foreign key constraints use the same naming convention as indexes. So, we will concatenate the table name and the columns in the constraint then suffix the name with "_foreign":

  1. $table->dropForeign('posts_user_id_foreign');

Or, you may pass an array value which will automatically use the conventional constraint name when dropping:

    You may enable or disable foreign key constraints within your migrations by using the following methods: