Bdtjtk

I am using laravel 5.7 and I noticed that my database table was not created after running php artisan migrate even when my .env has been properly updated and everything seems very correct from my angle.

After much research, I stumbled into a video that said I have to go to AppServiceProver.php and add some lines of codes as follows:

Update AppServiceProver.php from:

<?php



namespace AppProviders;



use IlluminateSupportServiceProvider;



class AppServiceProvider extends ServiceProvider

{

    /**

     * Bootstrap any application services.

     *

     * @return void

     */

    public function boot()

    {

       //

    }



    /**

     * Register any application services.

To:

<?php



namespace AppProviders; 



use IlluminateSupportServiceProvider;

use IlluminateSupportFacadesSchema;



class AppServiceProvider extends ServiceProvider

{

    /**

     * Bootstrap any application services.

     *

     * @return void

     */

    public function boot()

    {

        Schema::defaultStringLength(191);

    }



    /**

     * Register any application services.

A line of code was added on line 6 (use IlluminateSupportFacadesSchema;) and the Schema was called upon on line 17 (Schema::defaultStringLength(191);).

Immediately I added those lines of codes to my AppServiceProver.php, and then ran php artisan migrate; all my table just got created immediately on my database.

But the unfortunate thing for me as a learner is that the man said he doesn't know why the tables were not created at first and why the codes had to be added to AppServiceProvider.php. That he had the error and stumbled into the answer too.

As a learner, I am curious and want to know why I had that challenge and why those lines of codes solved them.

Thank you very much for your kind answers.

You have to set defaultStringLength to switch the character set, utf8mb4
The utf8mb4 character set is useful because nowadays we need support for storing not only language characters but also symbols, newly introduced emojis, and so on. Hope you got it!

Sorry for the late reply While running the migration you may get the error as

Specified key was too long; max key length is 767 bytes

this is because

Just For Example

You Migration may look

public function up()

    {

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

            $table->increments('id');

            $table->string('name');

            $table->string('email')->unique();

            $table->timestamp('email_verified_at')->nullable();

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

While running the migration it will look for length for the each field

such as

public function up()

        {

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

                $table->increments('id');

                $table->string('name',50);

                $table->string('email',100)->unique();

                $table->timestamp('email_verified_at',150)->nullable();

                $table->string('password',150);

                $table->rememberToken();

                $table->timestamps();

            });

        }

If you are lazy and need to add comman length to add all the fileds

use Schema::defaultStringLength(191); inside boot Method of AppServiceProvider

By Adding this IT will add the length of the fileds as 191

Thats it