I use Laravel 5.2 and want to change default user table's columns. I wrote
in the CreateUsersTable
public function up()
{
Schema::create('users', function (Blueprint $table) {
$table->increments('id');
$table->string('name');
$table->string('email')->unique();
$table->string('password');
$table->rememberToken();
$table->timestamps();
});
Schema::table('users', function ($table) {
$table->string('role');
$table->string('info');
$table->string('age');
$table->string('hobies');
$table->string('job');
});
}
and i run these commands in the git bash but user table didn't change.
php artisan migrate:refresh
php artisan migrate
How can i solve it?
You should run composer dumpauto -o after running php artisan migrate command to register new migrations, so they could be rolled back.
Try it. If it will not work, try to delete all tables, including migrations and run this command:
php artisan migrate:install
create new migration file and do something like this
public function up() {
DB::statement('ALTER TABLE user ADD some_field INT');// your query here
}
php artisan migrate
You only need to change what it inside of Schema::create and delete your Schema::table
Then, you need to implement tour down() mehod and add Schema::drop('users'); in order to drop your table when you run migrate:refresh.
You can read the 'Database migrations' in the laravel documentation for further details.
delete the first statement and leave last one only .
then run php artisan migrate:refresh
Related
I want to create a "users" table with the email record as a unique value with the Migrations file of my Laravel project
Schema::create('users', function (Blueprint $table) {
$table->id();
$table->string('company')->nullable();
$table->string('street', 80)->nullable();
$table->string('zip', 10)->nullable();
$table->string('city', 80)->nullable();
$table->string('country', 3)->nullable();
$table->string('firstname', 80)->nullable();
$table->string('lastname', 80)->nullable();
$table->string('email', 80);
$table->timestamp('email_verified_at')->nullable();
$table->string('password');
$table->timestamps();
});
works fine, but if I replace $table->string('email', 80); with $table->string('email', 80)->unique(); I get the error SQLSTATE[HY000] [2002] Connection refused (SQL: alter table usersadd uniqueusers_email_unique(email)) I read, that adding Schema::defaultStringLength(191); in AppServiceProvider.php would solve this, but even after adding it and clearing cache with php artisan config:clear && php artisan cache:clear && php artisan view:clear && php artisan route:clear the error is still there.
After trying a bit more I realised, that the error was with my mariadb version, as pointed out in this Comment MariaDB 10.4 supports a UNIQUE KEY on a TEXT column, so I changed $table->string('email')->unique() to $table->text('email')->unique() and it worked.
I am new to laravel.
I am working on laravel version 6.
I have created migration.
It works nicely the first time, but if i change something in the migration file and then i run php artisan migrate it shows nothing to migrate.
I tried php artisan migrate --path as well but it does not work.
To make it work i have to delete the migration file and create it again.
I don't want to use php artisan migrate:fresh.
what should i do to run only one migrations file which has been changed?
When you run php artisan migrate it'll check migration table if there is no new file in the migration folder it'll show you nothing to migrate.
If you want to rollback last migration.
To rollback the latest migration operation, you may use the rollback command. This command rolls back the last "batch" of migrations, which may include multiple migration files:
php artisan migrate:rollback
It'll delete the last created table.
The migrate:reset command will roll back all of your application's migrations:
php artisan migrate:reset
The migrate:fresh command will drop all tables.
php artisan migrate:fresh
php artisan migrate:fresh --seed
more info : document
Sadly impossible. The best workaround is to use seeders and use php artisan db:seed after you use php artisan migrate:fresh. Why don't you want to use that?
there is two things to do you that you can use
1. In your database there is a table called migrations. Delete the rows from there which one is you want to migrate. That should be there.
2.create a folder inside of database/migrations/folder. And put the migrations file inside the folder then in your command prompt run this below command:
php artisan migrate:refresh --path=database/migrations/folder
option 2 is better than the option 1. I always use this. So i recommend option 2. This should be work
If you have seeder data then you simply do: php artisan migrate: fresh -- seed . It help to re-migrate your migration with seeder data
You didn't understand well migrations mechanics.
but if i change something in the migration file and then i run php artisan migrate it shows nothing to migrate
You write migration to make some changes in database and run it once. If you want to do next updates to database you need next migration.
During development process you can rerun migrations by php artisan migrate:fresh, but on production make sure your migration makes everything you want.
Laravel stores informations about migrations in database in table 'migrations'. If you want to reset some migrations files you can try deleting or edit some records in that table.
Have you checked that the migration has already run or not in the migration table.
If its run then there will be a row respective to your migration.
If you do changes to an old migration than nothing will be reflected when you run command php artisan migrate, as it has already been migrated.
For every modification on existing (already migrated tables) you will have to make a new migration with modifications only. If you have "users" table migration 2014_10_12_000000_create_users_table like:
Schema::create('users', function (Blueprint $table) {
$table->bigIncrements('id');
$table->string('name');
$table->string('email')->unique();
$table->string('password');
$table->rememberToken();
$table->timestamps();
});
and you need to split "name" column, will have to php artisan make:migration alter_table_users --table="users" and add what you want to change:
Schema::table('users', function (Blueprint $table) {
$table->renameColumn('name', 'first_name'); // rename column
$table->string('last_name'); // add new column });
Reverse
public function down()
{
Schema::table('users', function (Blueprint $table) {
$table->renameColumn('first_name', 'name');
$table->dropColumn('last_name');
});
}
Nou you can use php artisan migrate
Documentation: https://laravel.com/docs/6.x/migrations#modifying-columns
No one replied question "Akshay Rathod" but "Militaru" replied exactly what he need php artisan make:migration alter_table_users --table="users" and copy you new fields inside the up() function as under
public function up()
{
Schema::table('users', function (Blueprint $table) {
$table->string('userimage')->nullable();
$table->string('contact_no')->nullable();
$table->string('website')->nullable();
$table->string('country_id')->nullable();
$table->string('timezone')->nullable();
$table->string('currency')->nullable();
$table->string('communication_email')->default(1);
$table->string('communication_phone')->default(0);
$table->string('allow_marketing')->default(0);
});
}
Having used the appropriate artisan commands:
php artisan make:model VenuesGeoNations --migration
... and:
php artisan make:model VenuesGeoRegions --migration
I created the schema:
Schema::create('venues_geo_nations', function (Blueprint $table) {
$table->increments('id');
$table->string('nation');
$table->string('iso');
$table->timestamps();
});
... and:
Schema::create('venues_geo_regions', function (Blueprint $table) {
$table->increments('id');
$table->string('towns_cities');
$table->string('regions');
$table->string('nations');
$table->mediumInteger('venues_geo_nation_id')->unsigned();
$table->foreign('venues_geo_nation_id')->references('id')->on('venues_geo_nations');
$table->timestamps();
});
However, when I run the migration command, I get the error:
[Illuminate\Database\QueryException] SQLSTATE[HY000]: General error:
1215 Cannot add foreign key constraint...
... on the venues_geo_regions table, in spite of the correct execution order.
I've also tried executing in the reverse order and I get the same error.
Compounding things is the fact that each rollback wipes out the tables for Voyager, and if it wasn't for snapshots on the EC2 instance I'm using, I'd have gone mad before now.
At this stage I'm a bit lost, and have to assume I'm doing something wrong.
I'm trying to modify a existing migration. Here is my current migration class:
class CreateLogForUserTable extends Migration
{
public function up()
{
Schema::create('log_for_user', function (Blueprint $table) {
$table->increments('id');
$table->integer('user_id');
$table->string('table_name');
$table->string('error_message');
$table->unsignedTinyInteger('error_code');
$table->timestamps();
});
}
public function down()
{
Schema::drop('log_for_user');
}
}
I've executed the php artisan migrate command once. Now I need to add ->nullable() method to the error_message column. So I edited my migration, something like this:
.
.
$table->string('error_message')->nullable();
.
.
But when I execute php artisan migrate again, it says:
Nothing to migrate.
How can I apply the new version of the migration?
You should create a new migration using command:
php artisan make:migration update_error_message_in_log_for_user_table
Then, in that created migration class, add this line, using the change method like this:
class UpdateLogForUserTable extends Migration
{
public function up()
{
Schema::table('log_for_user', function (Blueprint $table) {
$table->string('error_message')->nullable()->change();
});
}
public function down()
{
Schema::table('log_for_user', function (Blueprint $table) {
$table->string('error_message')->change();
});
}
}
To make these changes and run the migration, use the command:
php artisan migrate
and to rollback the changes, use the command:
php artisan migrate:rollback
You may rollback a limited number of migrations by providing the step option to the rollback command. For example, the following command will rollback the last five migrations:
php artisan migrate:rollback --step=5
See more about Modifying columns with Migration
If your app is not in production and you seed your data, the best you can do is to run:
php artisan migrate:refresh --seed
This command will drop all tables and recreate them. Then it will seed the data.
If you will create additional migrations for each change during development, you'll end up with hundreds of migrations classes.
You can use the change method, it allows you to modify some existing column types to a new type or modify the column's attributes.
For example modify a column to be nullable:
Schema::table('log_for_user', function ($table) {
$table->string('error_message')->nullable()->change();
});
But first of all you'll need the doctrine/dbal package
composer require doctrine/dbal
There is one more option. Roll back the migration, edit the file, and run it again.
This is a fairly common thing to do on a local development server while you're working out the bugs in a new piece of code. Using the method from the accepted answer, you might end up with 17 migrations for creating a single table!
php artisan migrate
# realize you've made an error
php artisan migrate:rollback
# edit your migration file
php artisan migrate
The number of steps back to take can be specified on the command line if needed.
# undo the last 3 migrations
php artisan migrate:rollback --step=3
Or you can specify a particular migration that needs undoing.
# undo one specific migration
php artisan migrate:rollback --path=./database/migrations/2014_10_12_100000_create_users_table.php
There are 2 ways to do this:
Run php artisan migrate:refresh. This will rollback all your
migrations and migrate all your migrations. If you run this command,
all the data inserted in your database will be lost.
Run php artisan make:migration enter_your_migration_name_here.
Then insert this in your migration:
$table->string('error_message')->nullable()->change();
Then run php artisan migrate to make your table changes. (Take note that when you do this, you have require composer require doctrine/dbal in your composer)
I tried to implement the default auth login system in laravel
php artisan make:migration create_users_table
Created Migration: 2016_03_10_115611_create_users_table
On running the above command only migration file is created and not the tables are created.
Also i have tried to reinstall composer but it didn't work
//In 2016_03_10_115611_create_users_table file
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
class CreateUsersTable extends Migration
{
/**
* Run the migrations.
*
* #return void
*/
public function up()
{
Schema::create('users', function (Blueprint $table) {
$table->increments('id');
$table->string('name');
$table->string('email')->unique();
$table->string('password');
$table->rememberToken();
$table->timestamps();
});
}
/**
* Reverse the migrations.
*
* #return void
*/
public function down()
{
Schema::drop('users');
}
}
on running
php artisan migrate
it took a few amounts of time and returned
[ErrorException]PDO::__construct(): MySQL server has gone away
Thanks to everyone i have not configured the .env file properly so that it doesn't work
What's your MySQL version?
Or you not yet modify .env
Try SQLite and change settings database to sqlite. I think this problem on php extension.
First you have run this command to install migration
php artisan migrate:install
Note :- if you look at database/migrations there will be already two migrations files
2014_10_12_000000_create_users_table.php
2014_10_12_100000_create_password_resets_table.php
php artisan migrate