Migration creation in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a migration in Laravel?

A migration is a way to create and modify database tables using PHP code. It helps keep database structure consistent and easy to share.

beginner

How do you create a new migration file in Laravel?

Use the command php artisan make:migration create_table_name in the terminal. This creates a new migration file in the database/migrations folder.

beginner

What are the two main methods inside a Laravel migration class?

The two main methods are up() and down(). up() defines the changes to apply, like creating tables. down() reverses those changes.

beginner

Why should you use migrations instead of manually changing the database?

Migrations keep your database changes organized and version-controlled. They make it easy to share changes with others and rollback if needed.

beginner

What command runs all pending migrations in Laravel?

Use php artisan migrate to apply all new migrations and update the database structure.

Which command creates a new migration file in Laravel?

A php artisan migrate:rollback

B php artisan migrate

C php artisan db:create

D php artisan make:migration

The command php artisan make:migration creates a new migration file.

What does the up() method in a migration do?

A Defines the changes to apply to the database

B Reverts database changes

C Deletes the migration file

D Runs database seeders

The up() method defines the changes like creating or modifying tables.

Where are migration files stored in a Laravel project?

A app/Models

B resources/views

C database/migrations

D public/migrations

Migration files are stored in the database/migrations folder.

Which command applies all new migrations to the database?

A php artisan migrate

B php artisan migrate:rollback

C php artisan make:migration

D php artisan db:seed

The php artisan migrate command runs all pending migrations.

What is the purpose of the down() method in a migration?

A To apply new changes

B To reverse the changes made by <code>up()</code>

C To create a new migration file

D To seed the database

The down() method reverses the changes made by up().

Explain the process of creating and running a migration in Laravel.

Think about the commands and methods involved.

Why are migrations important for managing database changes in a Laravel project?

Consider teamwork and safety in database updates.

Practice

1. What is the primary purpose of a migration in Laravel?

easy

A. To create and modify database tables in a structured way

B. To handle user authentication

C. To manage routes in the application

D. To compile CSS and JavaScript assets

Solution

1. Step 1: Understand migration role

   Migrations are designed to manage database schema changes safely and consistently.

2. Step 2: Compare with other options

   Options A, C, and D relate to authentication, routing, and asset compilation, which are not migration tasks.

3. Final Answer:

   To create and modify database tables in a structured way -> Option A

4. Quick Check:

   Migration = Manage database tables [OK]

Hint: Migrations always deal with database tables [OK]

Common Mistakes:

• Confusing migrations with routing or authentication
• Thinking migrations compile assets
• Assuming migrations handle user sessions

2. Which command correctly creates a new migration file in Laravel?

easy

A. php artisan migration:create users

B. php artisan make:migration create_users_table

C. php artisan new:migration users_table

D. php artisan create:migration users

Solution

1. Step 1: Recall Laravel migration command

   The correct command to create a migration is php artisan make:migration followed by the migration name.

2. Step 2: Check each option

   Only php artisan make:migration create_users_table uses the correct syntax and command name.

3. Final Answer:

   php artisan make:migration create_users_table -> Option B

4. Quick Check:

   Use 'make:migration' to create migrations [OK]

Hint: Use 'make:migration' command to create migrations [OK]

Common Mistakes:

• Using wrong artisan command names
• Omitting 'make:' prefix
• Confusing migration creation with other artisan commands

3. Given this migration snippet, what will happen when running php artisan migrate?

public function up()
{
    Schema::create('posts', function (Blueprint $table) {
        $table->id();
        $table->string('title');
        $table->text('content');
        $table->timestamps();
    });
}

medium

A. Updates the 'posts' table by adding new columns

B. Deletes the 'posts' table if it exists

C. Creates a 'posts' table with id, title, content, and timestamps columns

D. Throws an error because 'timestamps' is not a valid method

Solution

1. Step 1: Analyze the up() method

   The code uses Schema::create to make a new table named 'posts' with columns: id, title, content, and timestamps.

2. Step 2: Understand Laravel Schema methods

   $table->timestamps() adds created_at and updated_at columns automatically. This is valid and common.

3. Final Answer:

   Creates a 'posts' table with id, title, content, and timestamps columns -> Option C

4. Quick Check:

   Schema::create + columns = new table [OK]

Hint: Schema::create builds new tables with specified columns [OK]

Common Mistakes:

• Thinking timestamps() is invalid
• Confusing create with update
• Assuming it deletes tables

4. Identify the error in this migration code:

public function up()
{
    Schema::create('comments', function (Blueprint $table) {
        $table->increments('id');
        $table->string('text');
        $table->timestamps;
    });
}

medium

A. String column 'text' must have a length specified

B. Using increments instead of id method

C. Table name should be singular, not plural

D. Missing parentheses after timestamps method call

Solution

1. Step 1: Check method calls in migration

   $table->timestamps is missing parentheses. It should be $table->timestamps() to call the method.

2. Step 2: Validate other parts

   Using increments('id') is valid, plural table names are allowed, and string columns default length is 255 if not specified.

3. Final Answer:

   Missing parentheses after timestamps method call -> Option D

4. Quick Check:

   Method calls need parentheses () [OK]

Hint: Always add () when calling migration methods [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Thinking increments is invalid
• Believing table names must be singular

5. You want to create a migration that adds a nullable 'bio' text column to the existing 'users' table. Which up() method code is correct?

hard

A. Schema::table('users', function (Blueprint $table) {
$table->text('bio')->nullable();
});

B. Schema::create('users', function (Blueprint $table) {
$table->text('bio')->nullable();
});

C. Schema::modify('users', function (Blueprint $table) {
$table->text('bio')->nullable();
});

D. Schema::addColumn('users', 'bio', 'text')->nullable();

Solution

1. Step 1: Understand how to modify existing tables

   To add a column to an existing table, use Schema::table with a closure defining the new column.

2. Step 2: Evaluate each option

   Schema::table('users', function (Blueprint $table) { $table->text('bio')->nullable(); }); correctly uses Schema::table and adds a nullable text column. Schema::create('users', function (Blueprint $table) { $table->text('bio')->nullable(); }); tries to create a new table, which is wrong. Options A and D use invalid Schema methods.

3. Final Answer:

   Schema::table('users', function (Blueprint $table) { $table->text('bio')->nullable(); }); -> Option A

4. Quick Check:

   Use Schema::table to add columns [OK]

Hint: Use Schema::table to change existing tables [OK]

Common Mistakes:

• Using Schema::create instead of Schema::table
• Using non-existent Schema methods
• Forgetting nullable() for optional columns