511

I can't figure out how to add a new column to my existing database table using the Laravel framework.

I tried to edit the migration file using...

<?php

public function up()
{
    Schema::create('users', function ($table) {
        $table->integer("paid");
    });
}

In terminal, I execute php artisan migrate:install and migrate.

How do I add new columns?

3
  • 1
    It would be useful if you could include any errors you're getting; what do you expect to happen; and what actually happens? Commented May 28, 2013 at 12:24
  • 24
    Great question. There is a lot of migration documentation out there, and it shows you the API and how to create tables the FIRST TIME. Then it all fails as you develop your app more and need to modify your db structure. Commented Nov 11, 2016 at 17:25
  • 1
    You must use php artisan make:migration Commented Apr 21, 2022 at 17:22

22 Answers 22

1142

To create a migration, you may use the migrate:make command on the Artisan CLI. Use a specific name to avoid clashing with existing models

for Laravel 5+:

php artisan make:migration add_paid_to_users_table --table=users

for Laravel 3:

php artisan migrate:make add_paid_to_users

You then need to use the Schema::table() method (as you're accessing an existing table, not creating a new one). And you can add a column like this:

public function up()
{
    Schema::table('users', function($table) {
        $table->integer('paid');
    });
}

and don't forget to add the rollback option:

public function down()
{
    Schema::table('users', function($table) {
        $table->dropColumn('paid');
    });
}

Then you can run your migrations:

php artisan migrate

This is all well covered in the documentation for both Laravel 4 / Laravel 5:

And for Laravel 3:

Edit:

use $table->integer('paid')->after('whichever_column'); to add this field after specific column. applicable for MySQL only

Sign up to request clarification or add additional context in comments.

21 Comments

Just php artisan migrate
Something is wrong. I make "db:make" to make a new migration file. And then i put the Schema::table('users', function($table) { $table->integer('paid'); }); into it. And run "php artisan migrate", but getting Fatal error: Cannot redeclare class Users in /Applications/XAMPP/xamppfiles/htdocs/adsense/application/migrations/2013_05_28_122527_users.php on line 3
Creating migrations is also covered in the documentation. You should give it a more specific name, like "add_paid_to_users", this way it will not clash with your model clash.
As of Laravel 5, this command would now be php artisan make:migration add_paid_to_users
It is a good idea to do #php artisan migrate --pretend before #php artisan migrate just to check what is the migration will do before the migration is processed,
|
89

In case you want to add new column as a FOREIGN KEY to an existing table.

Create a new migration by executing this command : make:migration

Example :

php artisan make:migration add_store_id_to_users_table --table=users

In database/migrations folder you have new migration file, something like :

2018_08_08_093431_add_store_id_to_users_table.php (see the comments)

<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class AddStoreIdToUsersTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::table('users', function (Blueprint $table) {
            
            // 1. Create new column
            // You probably want to make the new column nullable
            $table->integer('store_id')->unsigned()->nullable()->after('password');
            
            // 2. Create foreign key constraints
            $table->foreign('store_id')->references('id')->on('stores')->onDelete('SET NULL');
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::table('users', function (Blueprint $table) {
            
            // 1. Drop foreign key constraints
            $table->dropForeign(['store_id']);

            // 2. Drop the column
            $table->dropColumn('store_id');
        });
    }
}

After that run the command :

php artisan migrate

In case you want to undo the last migration for any reason, run this command :

php artisan migrate:rollback

You can find more information about migrations in the docs

1 Comment

The rollback wont work like this. For rollback to work, $table->dropForeign('posts_store_id_foreign'); $table->dropColumn('store_id');
83

I'll add on to mike3875's answer for future readers using Laravel 5.1 and onward.

To make things quicker, you can use the flag "--table" like this:

php artisan make:migration add_paid_to_users --table="users"

This will add the up and down method content automatically:

/**
 * Run the migrations.
 *
 * @return void
 */
public function up()
{
    Schema::table('users', function (Blueprint $table) {
        //
    });
}

Similarily, you can use the --create["table_name"] option when creating new migrations which will add more boilerplate to your migrations. Small point, but helpful when doing loads of them!

2 Comments

That was not the case in Laravel 5.0, Blueprint was added in Laravel 5.1. Just a point of clarification is all.
@PhillSparks You're right, thank you for catching my mistake. I've updated to clarify the version in which this can be used.
30

If you're using Laravel 5, the command would be;

php artisan make:migration add_paid_to_users

All of the commands for making things (controllers, models, migrations etc) have been moved under the make: command.

php artisan migrate is still the same though.

Comments

27

In Laravel 8

php artisan make:migration add_columnname_to_tablename_table --table=tablename

then after creating migration in

public function up()
    {
        Schema::table('users', function (Blueprint $table) {

            // 1. Create new column
            $table->datatype('column_name')->nullable();
        });
    }
public function down()
    {
        Schema::table('users', function (Blueprint $table) {

            // 1. Create new column
            $table->dropColumn('column_name');
        });
    }

then run

php artisan migrate

if you face error then rename the migration name with the date before the table created and then run again php artisan migrate

1 Comment

Can we create seeder for the new col?
21

You can add new columns within the initial Schema::create method like this:

Schema::create('users', function($table) {
    $table->integer("paied");
    $table->string("title");
    $table->text("description");
    $table->timestamps();
});

If you have already created a table you can add additional columns to that table by creating a new migration and using the Schema::table method:

Schema::table('users', function($table) {
    $table->string("title");
    $table->text("description");
    $table->timestamps();
});

The documentation is fairly thorough about this, and hasn't changed too much from version 3 to version 4.

3 Comments

Something is wrong. I make "db:make" to make a new migration file. And then i put the Schema::table('users', function($table) { $table->integer('paid'); }); into it. And run "php artisan migrate", but getting Fatal error: Cannot redeclare class Users in /Applications/XAMPP/xamppfiles/htdocs/adsense/application/migrations/2013_05_28_122527_users.php on line 3
You should name each of the migrations something unique when creating them. Typically the initial create I'll name create_users_table, then if I'm adding columns: add_email_password_columns_to_users.
yeah as evolve says, surely its better to stick with original laravel design philosophies and only use the "add_" verb at front of each file to keep track of changes. this way its easier to track changes for version control etc because a new add file is created for every iteration. If you just went and kept modifying the "create_" it would be hard to know that x employee, had messed something up by removing an index, or adding a new column etc etc. at least that makes sense in my head! :)
15

Laravel 7

  1. Create a migration file using cli command:

    php artisan make:migration add_paid_to_users_table --table=users

  2. A file will be created in the migrations folder, open it in an editor.

  3. Add to the function up():

Schema::table('users', function (Blueprint $table) {
    // Create new column
    // You probably want to make the new column nullable
    $table->integer('paid')->nullable()->after('status');
}
  1. Add to the function down(), this will run in case migration fails for some reasons:

    $table->dropColumn('paid');

  2. Run migration using cli command:

    php artisan migrate


In case you want to add a column to the table to create a foreign key constraint:

In step 3 of the above process, you'll use the following code:

$table->bigInteger('address_id')->unsigned()->nullable()->after('tel_number');

$table->foreign('address_id')->references('id')->on('addresses')->onDelete('SET NULL');

In step 4 of the above process, you'll use the following code:

// 1. Drop foreign key constraints
$table->dropForeign(['address_id']);
// 2. Drop the column
$table->dropColumn('address_id');

3 Comments

I am very new to Laravel. It is supposed to make things easier and I can see that. However, why would I do all of the above if I want to add a column to my table? Why would I not just add it to the sql table directly via phpmyadmin or the mysql CLI? Again I am new. It appears that there will be a lot of one-time code created if I am interpreting these answers correctly.
@MichaelB Well, Laravel recommends to use Migrations to add new tables or fields to current tables or create relations. Why? Because at the time moving to 'Production Environment' (Live website) from 'Development Environment', you don't have to create all those tables and relations in database by your own. You just need to upload the files to server, update .env file and run the migration command. Laravel will create the tables with relations for you.
Thank you Rehan Arshad, this command still works on Laravel 10. In my case I directly use the command on terminal. $ php artisan make:migration add_paid_to_users_table
12

This approach works on Laravel 5.1.

First, execute the following command in your terminal:

php artisan make:migration add_paid_to_users --table=users

after that go to your project directory and expand directory database - migration and edit file add_paid_to_users.php, add this code

public function up()
{
    Schema::table('users', function (Blueprint $table) {
         $table->string('paid'); //just add this line
    });
}

Next, return to your terminal and run the following command:

php artisan migrate

I hope this is helpful.

Comments

8

First rollback your previous migration

php artisan migrate:rollback

After that, you can modify your existing migration file (add new , rename or delete columns) then Re-Run your migration file

php artisan migrate

Comments

8

STEP 1

php artisan make:migration add_sex_to_users_table --table=users

STEP 2

In the newly generated migration file, you will find up and down hook methods. in up hook, add there columns that you want to add, and in down hook, add there columns that you need to remove. for example, Me i need to add sex on column of users, so I will add there following line in the up hook.

$table->integer('quantity')->default(1)->nullable();

So I have something like this

public function up()
{
    Schema::table('service_subscriptions', function (Blueprint $table) {
        $table->integer('quantity')->default(1)->nullable();
    });
}

STEP 3

Run the migration command as follows

php artisan migrate

Then you will have a new column added

Comments

5

WARNING: this is a destructive action. If you use this ensure you back up your database first.

You can simply modify your existing migration file, for example adding a column in your table, and then in your terminal typing :

$ php artisan migrate:refresh

4 Comments

Refresh will empty the table
This is incredibly dangerous - if some people have the run the old version, some will have the new, and chaos will ensue. In Liquibase, if you edit a file, it will fail unless you explicitly put in exceptions to allow it, and you can only do this in very few cases. E.g. if you make a column not-null when some database already have null data in them, it will break.
It would be better, if you edit your answer and mention that it would empty your table, it would be better.
Note: This command will clean entire databases tables, if you want to use it, then backup your database first
5

From solution of mikelovelyuk, I removed the --table

Using Laravel 10

php artisan make:migration add_paid_to_users

Inside the Migration file For instance 2023_06_21_071221_add_paid_to_users_table

public function up(): void
{
    Schema::table('users', function (Blueprint $table) {
       $table->string('paid')->nullable();
    });
}

/**
* Reverse the migrations.
*/
public function down(): void
{
    Schema::table('users', function (Blueprint $table) {
        $table->dropColumn('paid');
    });
}

Then migrate

php artisan migrate

3 Comments

Actually you can just write add_to_users, he will not generate code for column definition anyway.
Hi @devope, I believe this comment of mine was about adding column from an existing table on a schema. I used add_to_paid_users, due the question is about to make the migration file to add paid column. My solution is to make the migration file specific, and descriptive, this is a best practice approach when adding columns, because symantically "add_to_paid_users" migration file means adding paid column to users table. Please correct me if I'm wrong. Peace be with us.
workd for me thanks.
4

Add column to your migration file and run this command.

php artisan migrate:refresh --path=/database/migrations/your_file_name.php

Comments

2

In laravel 8

php artisan make:migration add_paid_to_users_table --table=users

public function up()
 {
    Schema::table('users', function($table) {

        $table->integer('paid');

  });

}

In laravel 9

add a new column in existing table

php artisan make:migration add_paid_to_users_table

if you want to create new migration then do the below code

php artisan make:migration create_users_table --create=users

Comments

1

First you have to create a migration, you can use the migrate:make command on the laravel artisan CLI.Old laravel version like laravel 4 you may use this command for Laravel 4:

php artisan migrate:make add_paid_to_users

And for laravel 5 version

for Laravel 5+:

php artisan make:migration add_paid_to_users_table --table=users

Then you need to use the Schema::table() . And you have to add the column:

public function up()

{

    Schema::table('users', function($table) {

        $table->integer('paid');

    });

}

Comments

0

If you want to add a new field for the first column, proceed with this method

For Example Users Db

php artisan make:migration add_new_field_ID_to_users

After Open New Migration In Database=>migrations

/**

  • Run the migrations.

  • @return void */

    public function up() { Schema::table('users', function (Blueprint $table) { $tabale->id()->first() }); }

With this method, you add the ID as the first field of the table and the data inside the table will not be lost

After Run : php artisan migrate

Comments

-1

Although a migration file is best practice as others have mentioned, in a pinch you can also add a column with tinker.

$ php artisan tinker

Here's an example one-liner for the terminal:

Schema::table('users', function(\Illuminate\Database\Schema\Blueprint $table){ $table->integer('paid'); })



(Here it is formatted for readability)

Schema::table('users', function(\Illuminate\Database\Schema\Blueprint $table){ 
    $table->integer('paid'); 
});

1 Comment

The answers offered nice advice but could be marked as non-relevant to the current topic.
-1

If you don't want to split the blueprint(schema) into two migration file then the best thing you can do is drop the table from the database and then rename the migration file's last number and do

php artisan migrate

This helps you to protect the data of other tables.

Comments

-1

Run this command: php artisan migrate:fresh --seed it will drop the table and re add it updating all the columns adding to the database

2 Comments

In a production environment, you don't want to refresh tables just to add a new column.
This is not the best practice, this is a quick solution for fresh dummy data sets.
-1

What you can do is Like,

Schema::create('users', function ($table) { $table->integer("paid"); });

After Writing this write command php artisan migrate or php artisan refresh What i personally prefer is to refresh rather than fresh migration because if you do fresh migrate it will remove all the data refresh will not.

but only exception is if you do refresh and if you have any foreign key in table so it will not going to re-establish the relationship so you will get error like,

Cannot add foreign key constrain

2 Comments

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.
It is Ok you tried to offer solution however, this answer could lead to danger for beginners working on real operational data without backup SQL files. Refreshing a migration file would lead to permanent deletion of records. These commands such as php artisan migrate woun't take effect. On the other hand php artisan refresh is an incomplete command. Please correct me if I'm wrong.
-1

If none of the solve worked, you might have recreated the migration file then added a new column and tried to run php artisan migrate to update the old table which will try to create that table but the table already exists so it gives an error. To solve that rename the migration file as previously named (started with a date), then add new column run php artisan migrate that will actually update the old one instead of create, solved my problem.

Comments

-1

You can also run the migration in this way:

php artisan make:migration 'add column paid to users table'

Then proceed to enter the column and the datatype in the new migration created:

public function up()
{
    Schema::create('users', function ($table) {
        $table->integer("paid");
    });
}

1 Comment

This pseudo logic is correct, however wrong solution—It is suggested to complete the syntax.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.