Laravel Migration

laravel

Introduction

Migration is like an update assurance for your software, allowing the team to quickly change and distribute the software scheme for the application. Usually, migrations are combined with Laravel's schema builder to quickly construct the database schema for your query. If you have ever had to tell a colleague to connect a column individually to their regional database schema, you've faced the issue of database migration solve

The Laravel Schema framework offers agnostic support for the database to build and modify tables across all Laravel's supported database systems.

Generating Migrations

To create a migration, here we will use the make: migration Artisan command:

PHP artisan make: migration message_you_want_to_remember

Place the latest transfer in your application/migrations folder. Which name of the transfer file includes a timestamp allowing Laravel to decide the migration order.

The terms —table and —create can be used to signify the position name, whether a new column will be created by the migrate. These options pre-fill the created stub migration file with the table is given:

PHP artisan make: migration create_blogs_table --create=blogs

//PHP artisan make:migration add_votes_to_blogs_table --table=blogs

When performing the make: transfer request, you can use the —path option if you want to specify a customized destination path for the created integration. The given pathway should be proportional to the base path of your submission.

Migration Structure

A migration class includes two techniques: upwards and downwards. The up method can be used to add additional tables, columns, or directories to the database, whereas the down method will reverse the up method operations.

In any of those methods, you can elegantly create and change tables using the Laravel Schema Builder. Look out the information to learn about all the options available on the Schema creator. For example, this example of migration produces a table of flights:

<?php

use Illuminate\Support\Facades\Schema; 

use Illuminate\Database\Schema\Blueprint; 

use Illuminate\Database\Migrations\Migration; 

 

class CreateBlogsTable extends Migration 

{ 

    /**

     * Run the migrations.

     *

     * @return void

     */ 

    public function up() 

    { 

            Schema::create('blogs', function (Blueprint $table) { 

            $table->bigIncrements('id'); 

            $table->string('title'); 

            $table->string('desciption'); 

            $table->rememberToken(); 

            $table->timestamps(); 

        }); 

    } 

 

    /**

     * Reverse the migrations.

     *

     * @return void

     */ 

    public function down() 

    { 

        Schema::dropIfExists('blogs'); 

    } 

}

?>

Running Migrations

so now if you want to run all of your outstanding migrations, execute the migrate Artisan command:

PHP artisan migrate

When you use the windows system from Farmstead, you can run the control from inside your windows machine.

Forcing Migrations To Run in Production

Some transformation operations are harmful, meaning that they can cause data loss. To stop you from operating these instructions against your development database, you'll be prompted for confirmation before executing the commands. To compel commands to run with no request, use the flag —control:

PHP artisan migrate --force

Read More...
Also, Visit Here  PHP Tutorial