Skip to main content

Create MySQL tables

Create MySQL tables

Creating MySQL database tables from Laravel

To follow Laravel standards, We should create a table using Laravel artisan commands. It will help to other teammates automatically update database changes just with one command. To create a table use below command.

php artisan make:migration create_yourTableName_table

It will create a table and you can also check the migrate files in the below path

mylaravel\database\migrations\

Let's create sample table name called "posts"

php artisan make:migration create_posts_table

Creating "posts" Table




After run this command, Migration file will be created. you can check the migration folder


Migration file

Let's add some columns in the posts table
public function up()
    {
        Schema::create('posts', function (Blueprint $table) {
            $table->id();
            $table->string('slug');
            $table->text('body');
            $table->timestamp('publised_at')->nullable();
            $table->timestamps();
        });
    }
before running migration, Let's see the MySQL database

Before running migrate

After running migration php artisan migrate

 

It will add some default Laravel migrations also, now check at database

posts table created


columns are added


Suppose If I want to add another column to the "posts" table. Like 'title' column.

In this case, you can simple run the migration command
php artisan make:migration add_title_to_posts_table

Creates one more migration file




Migration file



As discussed it creates one more migration file, now we need to add our "title" column here as well as we need to write down() method for drop the changes.

Add title column


run the migrate command again





Title column added


Will do this kind of approach if your project is on production. otherwise you can add "title" in "posts" migration file directly. 

At the same way if want to undo the last migration. You can run
php artisan migrate:rollback

Undo the last migration





Now you can add the "title" column directly to "posts" migration file.

"title" column added at "posts" migration file.


But here, After add the "title" column in "posts" migration file. And run the 

php artisan migrate


Nothing to migrate

it will run nothing, Because that migration file already read. so you need to rollback all tables once again.
php artisan migrate:rollback

Rollback all tables


and again need to run the command
php artisan migrate

now it will create all tables once again.

Note: every time you do this, all table data will be deleted.
Important: so that's when you are in production, you will be careful with this actions
So now, if you refresh MySQL tables, all tables are created.

All tables are created with my additional "title" column

In the second approach, You can run the 
php artisan migrate:fresh

this command will drop all the tables and create new fresh tables
Created all tables












Comments

Popular posts from this blog

Laravel Commands

Laravale commands #Check route list php artisan route:list #Check upload files links php artisan storage:link #Check database connected or not php artisan db #Make Request file php artisan make:request YourNameRequest #Make Controller #(In this statement you used -r -> resources and -m -> model. It will create CustomersController and Customers Model files) php artisan make:controller CustomersController -r -m Customers #Make Resource file php artisan make:resource CustomersResource #To check migration files status that those files are running or not with below commands php artisan migrate:status #To check if there is any pending migrate files to run #(also this command shows us the mysql query before running migration file) php artisan migrate --pretend #To make a database table (in this example Products name as taken) php artisan make:migration create_products_table #To create a Request file php artisan make:request StoreProductRequest php artisan make:request Up

Mysql columns creation in laravel

List of columns  $table->id(); // increment value $table->string('title')->comment('this is blog title'); $table->string('slug')->unique(); $table->text('short_desc'); $table->longText('description'); $table->boolean('is_published')->default(false); $table->integer('min_of_read')->nullable(true); $table->enum('status', ['Active', 'Inactive']); $table->float('discount'); $table->smallInteger('type_id'); $table->date('start_date')->nullable(); $table->timestamps(); $table->foreign('created_by')->references('id')->on('users'); // introducing foreign key $table->unsignedBigInteger('user_id'); //? $table->decimal('latitude', 9, 6)->nullable(true); // Let's say you want starting value from 1000 $table->id()->from(1000); // increment value start from 1000 ->nullabl

React Advanced JSX

 class vs className This lesson will cover more advanced JSX. You’ll learn some powerful tricks and some common errors to avoid. Grammar in JSX is mostly the same as in HTML, but there are subtle differences to watch out for. The most frequent of these involves the word class. In HTML, it’s common to use class as an attribute name: <h1 class = "big" > Title </h1> In JSX, you can’t use the word  class ! You have to use  className  instead: <h1 className = "big" > Title </h1> This is because JSX gets translated into JavaScript, and  class  is a reserved word in JavaScript. When JSX is  rendered , JSX  className  attributes are automatically rendered as  class  attributes. Self-Closing Tags Another common JSX error involves  self-closing tags . What’s a self-closing tag? Most HTML elements use two tags: an  opening tag  ( <div> ), and a  closing tag  ( </div> ). However, some HTML elements such as  <img>  and  <input>  u