This article explains Yii's database migration system for managing schema changes. It details creating, applying, and reverting migrations using yii migrate commands, emphasizing atomic changes, reversible up()/down() methods, and helper functions.

How to Use Yii's Database Migrations to Manage Schema Changes

Yii's database migrations provide a robust and version-controlled way to manage changes to your database schema. The core concept involves creating migration classes, each representing a single, atomic change to your database. These changes are typically additions, modifications, or deletions of tables, columns, indexes, and relationships.

Here's a breakdown of the process:

1. Creating a Migration: You use the yii migrate/create command to generate a new migration file. This command prompts you for a name, which is then used to create a PHP class extending yii\db\Migration. This class will contain up() and down() methods.
2. Defining Changes in up() and down(): The up() method contains the SQL statements to apply the schema changes. The down() method contains the reverse SQL statements to undo these changes, crucial for rollbacks. Yii provides helper methods like createTable(), addColumn(), dropColumn(), dropTable(), etc., making it easier to write migrations.
3. Applying Migrations: The yii migrate command applies all pending migrations (migrations that haven't been applied yet, based on the migration history table). This executes the up() methods of the unapplied migrations.
4. Reverting Migrations: The yii migrate/down command reverts the most recently applied migration by executing its down() method. You can specify a number to revert multiple migrations.
5. Migration History: Yii maintains a migration history table to track which migrations have been applied. This ensures that migrations are applied only once and in the correct order.

Example: A migration to create a users table might look like this:

<?php

use yii\db\Migration;

class m231027_100000_create_users_table extends Migration
{
    public function up()
    {
        $this->createTable('users', [
            'id' => $this->primaryKey(),
            'username' => $this->string(255)->notNull()->unique(),
            'email' => $this->string(255)->notNull()->unique(),
            'password_hash' => $this->string(255)->notNull(),
            'created_at' => $this->integer()->notNull(),
            'updated_at' => $this->integer()->notNull(),
        ]);
    }

    public function down()
    {
        $this->dropTable('users');
    }
}

Best Practices for Writing Effective Yii Database Migrations

Writing effective database migrations is key to maintaining a clean and manageable database schema. Here are some best practices:

• Keep Migrations Atomic: Each migration should represent a single, self-contained change. Avoid combining multiple unrelated changes into a single migration. This makes it easier to track changes, revert selectively, and understand the history of your database.
• Use Descriptive Names: Give your migration files clear and descriptive names reflecting the changes they make (e.g., m231027_100000_add_user_profile_table). The timestamp prefix ensures proper ordering.
• Write Reversible down() Methods: Always implement the down() method to reverse the changes made in up(). This is crucial for rollbacks and ensures data integrity. Test your down() methods thoroughly.
• Use Yii's Helper Methods: Utilize Yii's provided helper methods (createTable(), addColumn(), addForeignKey(), etc.) instead of writing raw SQL. This improves readability and portability across different database systems.
• Version Control Migrations: Store your migration files in your version control system (like Git) to track changes and collaborate effectively.
• Test Thoroughly: Before applying migrations to a production database, test them thoroughly in a development or staging environment.
• Avoid Data Manipulation in Migrations: While possible, avoid manipulating data within migrations unless absolutely necessary. Data seeding should generally be handled separately.

Handling Potential Conflicts or Rollbacks When Using Yii Database Migrations

Conflicts can arise if multiple developers work simultaneously on migrations or if a migration fails halfway. Yii provides mechanisms to handle these situations:

• Migration History Table: The migration history table prevents re-application of already applied migrations, minimizing the risk of conflicts.
• Rollback Mechanism: The yii migrate/down command allows reverting migrations to a previous state, undoing unwanted or failed changes.
• Transaction Management: Yii's migrations implicitly use transactions. If any part of a migration's up() method fails, the entire migration is rolled back automatically, preserving data integrity.
• Manual Resolution: In rare cases of complex conflicts, you might need to manually resolve them by editing the migration files or the migration history table. Exercise extreme caution when doing so.
• Concurrency Control: For collaborative development, consider implementing a workflow that ensures only one developer applies migrations at a time, perhaps using a locking mechanism or a centralized migration deployment process.

Using Yii Migrations to Manage Data Seeding Alongside Schema Changes

While primarily intended for schema changes, Yii migrations can be extended to handle data seeding. However, it's generally considered best practice to separate data seeding from schema migrations.

Here's why:

• Separation of Concerns: Keeping schema changes and data seeding separate improves clarity and maintainability. Schema migrations focus on database structure, while data seeding focuses on populating the database with initial data.
• Easier Rollbacks: If a data seeding issue occurs, rolling back a migration containing both schema and data changes is more complex than rolling back a simple schema migration.
• Flexibility: Separating allows you to easily re-seed your database without re-applying schema changes.

However, if you must include seeding, you can add data insertion logic within the up() method of your migration. Remember to include the corresponding data deletion in the down() method to allow for proper rollbacks. This approach is generally discouraged for large datasets. Consider using yii migrate/create to generate separate migrations specifically for data seeding, making the process more organized. Alternatively, consider using fixture data or a dedicated data seeding script for larger, more complex data sets.

The above is the detailed content of How do I use Yii's database migrations to manage schema changes?. For more information, please follow other related articles on the PHP Chinese website!