Laravel migration is a database version control tool that defines and modifies database structure through PHP code to improve collaboration efficiency and environmental consistency. The migration file contains up() and down() methods. The former is used to create or modify database elements, such as tables and fields, and the latter is used to roll back changes. For example, when creating a "users" table, the up() method defines the table structure, and the down() method deletes the table. Laravel provides Artisan command to simplify the migration process: use php artisan make:migration to generate migration files. When creating a model, you can use php artisan make:model User -mf command to execute migration. Use php artisan migrate to rollback. Use php artisan migrate:rollback to reset. Compared with direct operation of the database, migration ensures smooth team collaboration, avoids manual SQL errors, supports cross-environment reuse and provides a convenient rollback mechanism, greatly reducing human errors and repeated labor.

Migrations in Laravel are like version control for your database. They let you define and modify your database structure using PHP code, so you can keep your schema organized, share it with others, and apply changes safely across different environments (like local, staging, production).

This makes it easy to collaborate with other developers and ensures everyone is working with the same database structure — no more guessing what table or column names should be.

What do Laravel migrations look like?

A migration file includes two main methods: up() and down() . The up() method adds or modify database elements (like tables or columns), while down() rolls those changes back.

For example, if you create a migration to add a "users" table, the up() method would define how to create that table, and down() would drop it.

Here's a basic example of what a migration might look like:

 public function up()
{
    Schema::create('users', function (Blueprint $table) {
        $table->id();
        $table->string('name');
        $table->string('email')->unique();
        $table->timestamps();
    });
}

public function down()
{
    Schema::dropIfExists('users');
}

You don't have to write these manually from scratch — Laravel can generate them for you.

How to create and run migrations

Laravel gives you simple Artisan commands to manage migrations.

To create a new migration file, you can use:

 php artisan make:migration create_users_table

Or if you're creating a model along with the migration:

 php artisan make:model User -mf

That -mf flag creates a model, factory, and a migration all at once.

Once your migration is ready, you run it with:

 php artisan migrate

This applies all pending migrations. If you want to roll back the last batch of migrations (for example, if something went wrong), you can use:

 php artisan migrate:rollback

And if you really want to start over:

 php artisan migrate:fresh

This drops all tables and re-runs all migrations from scratch.

Why using migrations is better than editing the DB directly

• Collaboration : Everyone on the team can stay in sync without manually updating each other's databases.
• Consistency : You avoid mistakes that come from writing raw SQL by hand.
• Reusability : Migrations can be reused across different environments.
• Rollbacks : You can undo changes easily if something breaks.

Without migrations, you'd have to remember every change you made to the database and manually reapply them somewhere else — which is error-prone and time-consuming.

So yeah, migrations are basically a safe, repeatable way to manage your database structure in Laravel. Once you get used to them, you'll probably never want to go back to writing raw SQL again.

The above is the detailed content of What are migrations in Laravel, and how are they used?. For more information, please follow other related articles on the PHP Chinese website!