Reputation: 3079
Table 'users':
|id|name|address|post_code|deleted_at|created_at|
and I want add column 'phone_nr' somewhere between 'id' and 'deleted_at'
Is it possible by migrations in Laravel 4.1?
Upvotes: 76
Views: 136729
Reputation: 1216
As of Laravel 5.1, you can also position a new (mysql) column first. This was tested with Laravel 6:
Schema::table('foo', function (Blueprint $table) {
$table->increments('id')->first();
});
Upvotes: 2
Reputation: 155
If you need add several columns after specific column in laravel 8:
When using the MySQL database, the after method may be used to add columns after an existing column in the schema:
$table->after('password', function ($table) {
$table->string('address_line1');
$table->string('address_line2');
$table->string('city');
});
https://laravel.com/docs/8.x/migrations#column-order
Upvotes: 16
Reputation: 483
For latest versions of Laravel say 5-6
The command is
php artisan make:migration update_users_table
Then
php artisan migrate
Upvotes: -3
Reputation: 1161
For anyone else wondering about @rahulsingh's query about adding multiple columns back to back after a single specific column:
$table->integer('col1')->after('ref_col');
$table->integer('col2')->after('what');
You can do this just by writing the new fields in reverse order, for example:
$table->integer('col4')->after('ref_col');
$table->integer('col3')->after('ref_col');
$table->integer('col2')->after('ref_col');
$table->integer('col1')->after('ref_col');
When you run this migration you'll find that your new fields col
, col2
, ... are in your intended order after the reference field ref_col
.
Unfortunately there is no before()
function for adding fields before an existing field. (If that existed we could keep the above statements in their real order.)
You cannot do chaining with fields that do not yet exist, for example:
$table->integer('col1')->after('ref_col');
$table->integer('col2')->after('col1');
$table->integer('col3')->after('col2');
$table->integer('col4')->after('col3');
This is because the migration blueprint is compiled to a single query thus executed as one, so when it comes to adding col2
your database engine will complain that col1
doesn't exist.
Upvotes: 20
Reputation: 2883
Yes. Create a new migration using php artisan migrate:make update_users_table
.
Then use the table
command as follows (if you're using MySQL!):
Schema::table('users', function($table)
{
$table->string('phone_nr')->after('id');
});
Once you've finished your migration, save it and run it using php artisan migrate
and your table will be updated.
Documentation: https://laravel.com/docs/4.2/migrations#column-modifiers
Upvotes: 204
Reputation: 2911
The answer by James is still correct. However, Laravel 5 has slightly changed the make migration syntax:
php artisan make:migration add_google_auth_to_users_table --table=users
(I am aware this question is tagged Laravel 4, however it ranks quite high for the question ;) )
Upvotes: 16