Laravel Migration Error: Syntax error or access violation: 1071 Specified key was too long; max key length is...

86

Migration error on Laravel 5.4 with php artisan make:auth

[IlluminateDatabaseQueryException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter tabl e users add unique users_email_unique(email))

[PDOException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

mysql laravel pdo laravel-5 laravel-5.4

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer
  
  – Can Vural
  Feb 15 '17 at 9:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the suggestion @can-vural, I did.
  
  – absiddiqueLive
  Feb 15 '17 at 9:57
  
  
  

  
  
  
  

add a comment | 

86

Migration error on Laravel 5.4 with php artisan make:auth

[IlluminateDatabaseQueryException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter tabl e users add unique users_email_unique(email))

[PDOException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

mysql laravel pdo laravel-5 laravel-5.4

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer
  
  – Can Vural
  Feb 15 '17 at 9:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the suggestion @can-vural, I did.
  
  – absiddiqueLive
  Feb 15 '17 at 9:57
  
  
  

  
  
  
  

add a comment | 

86

86

86

23

Migration error on Laravel 5.4 with php artisan make:auth

[IlluminateDatabaseQueryException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter tabl e users add unique users_email_unique(email))

[PDOException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

mysql laravel pdo laravel-5 laravel-5.4

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

Migration error on Laravel 5.4 with php artisan make:auth

[IlluminateDatabaseQueryException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter tabl e users add unique users_email_unique(email))

[PDOException] SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

mysql laravel pdo laravel-5 laravel-5.4

mysql laravel pdo laravel-5 laravel-5.4

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

share|improve this question

share|improve this question

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

edited Apr 22 '17 at 16:05

Peter Mortensen

13.7k1986113

13.7k1986113

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

asked Feb 15 '17 at 8:49

absiddiqueLiveabsiddiqueLive

3,53821327

3,53821327

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer
  
  – Can Vural
  Feb 15 '17 at 9:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the suggestion @can-vural, I did.
  
  – absiddiqueLive
  Feb 15 '17 at 9:57
  
  
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer
  
  – Can Vural
  Feb 15 '17 at 9:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for the suggestion @can-vural, I did.
  
  – absiddiqueLive
  Feb 15 '17 at 9:57
  
  
  

  
  
  
  

3

3

You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer

– Can Vural
Feb 15 '17 at 9:35

You should answer your question in an answer. Not in the question. stackoverflow.com/help/self-answer

– Can Vural
Feb 15 '17 at 9:35

Thanks for the suggestion @can-vural, I did.

– absiddiqueLive
Feb 15 '17 at 9:57

Thanks for the suggestion @can-vural, I did.

– absiddiqueLive
Feb 15 '17 at 9:57

add a comment | 

26 Answers
26

active

oldest

votes

124

According to the official documentation, you can solve this quite easily.

Add following code to AppServiceProvider.php (/app/Providers/AppServiceProvider.php)

use IlluminateSupportFacadesSchema; //NEW: Import Schema



function boot()

{

    Schema::defaultStringLength(191); //NEW: Increase StringLength

}

MySQL reserves always the max amount for a UTF8 field which is 4 bytes so with 255 + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; you are over the 767 max key length limit. By @scaisedge

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.
  
  – shock_gone_wild
  Feb 16 '17 at 12:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…
  
  – absiddiqueLive
  Feb 17 '17 at 7:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.
  
  – shock_gone_wild
  Feb 17 '17 at 9:48
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  why exactly 191 characters @absiddiqueLive
  
  – PseudoAj
  Jun 15 '17 at 7:56
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  working on 5.7.0 . but why 191?
  
  – romal tandel
  Sep 5 '18 at 9:19
  

  
  
  
  

 | 
show 4 more comments

59

I don't know why the above solution and the official solution which is adding

Schema::defaultStringLength(191);

in AppServiceProvider didn't work for me.
What worked for was editing the database.php file in config folder.
Just edit

'charset' => 'utf8mb4',

'collation' => 'utf8mb4_unicode_ci',

to

'charset' => 'utf8',

'collation' => 'utf8_unicode_ci',

and it should work.
Hope it helps.

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593
  
  – Jeff Puckett
  Sep 27 '17 at 19:01
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thankyou really help..
  
  – Stefen Wiranata
  Mar 29 '18 at 9:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Still not worked! Any idea??
  
  – Hiren Gohel
  Apr 25 '18 at 11:37
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I think you missed this part use IlluminateSupportFacadesSchema; at the top.
  
  – pimpace
  Aug 18 '18 at 19:53
  
  
  

  
  
  
  

add a comment | 

32

I'm just adding this answer here as it's the quickest solution for me. Just set the default database engine to 'InnoDB' on

/config/database.php

'mysql' => [

    ...,

    ...,

    'engine' => 'InnoDB',

 ]

then run php artisan config:cache to clear and refresh the configuration cache

share|improve this answer

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Works perfect thank you.
  
  – PHPFan
  Oct 25 '18 at 21:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  changing engine from null to InnoDB worked
  
  – merdan
  Dec 13 '18 at 12:43
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  This should be marked as the best solution
  
  – Hazem Emad
  Jan 29 at 11:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This should be the accepted solution - Thanks
  
  – Tricky
  Feb 26 at 13:49
  

  
  
  
  

add a comment | 

21

In the AppServiceProvider.php,you include this code top of the file.

use IlluminateSupportFacadesSchema;

And you add this code in boot method.

 Schema::defaultStringLength(191);

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

add a comment | 

17

This issue is caused in Laravel 5.4 by the database version.

According to the docs (in the Index Lengths & MySQL / MariaDB section):

Laravel uses the utf8mb4 character set by default, which includes
support for storing "emojis" in the database. If you are running a
version of MySQL older than the 5.7.7 release or MariaDB older than
the 10.2.2 release, you may need to manually configure the default
string length generated by migrations in order for MySQL to create
indexes for them. You may configure this by calling the
Schema::defaultStringLength method within your AppServiceProvider.

In other words, in <ROOT>/app/Providers/AppServiceProvider.php:

// Import Schema

use IlluminateSupportFacadesSchema;

// ...



class AppServiceProvider extends ServiceProvider

{



public function boot()

{

    // Add the following line

    Schema::defaultStringLength(191);

}



// ...



}

But as the comment on the other answer says:

Be careful about this solution. If you index email fields for example,
stored emails can only have a max length of 191 chars. This is less
than the official RFC states.

So the documentation also proposes another solution:

Alternatively, you may enable the innodb_large_prefix option for your
database. Refer to your database's documentation for instructions on
how to properly enable this option.

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

add a comment | 

12

For someone who don't want to change AppServiceProvider.php.
(In my opinion, it's bad idea to change AppServiceProvider.php just for migration)

You can add back the data length to the migration file under database/migrations/ as below:

create_users_table.php

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

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

create_password_resets_table.php

$table->string('email',128)->index();

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This can be a problem since emails can be up to 255(ish) characters
  
  – Half Crazed
  Jun 18 '17 at 1:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272
  
  – helloroy
  Jun 19 '17 at 1:17
  

  
  
  
  

add a comment | 

6

I have solved this issue and edited my config->database.php file to like my database ('charset'=>'utf8') and the ('collation'=>'utf8_general_ci'), so my problem is solved the code as follow:

'mysql' => [

        'driver' => 'mysql',

        'host' => env('DB_HOST', '127.0.0.1'),

        'port' => env('DB_PORT', '3306'),

        'database' => env('DB_DATABASE', 'forge'),

        'username' => env('DB_USERNAME', 'forge'),

        'password' => env('DB_PASSWORD', ''),

        'unix_socket' => env('DB_SOCKET', ''),

        'charset' => 'utf8',

        'collation' => 'utf8_general_ci',

        'prefix' => '',

        'strict' => true,

        'engine' => null,

    ],

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

add a comment | 

6

Add the below code in app/Providers/AppServiceProvider.php method:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

first you have to delete (if you have) users table,
password_resets table from the database and delete users and password_resets entries from migrations table and then after deleting old tables run php artisan migrate command

share|improve this answer

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

add a comment | 

5

Instead of setting a limit on length I would propose the following, which has worked for me.

Inside

config/database.php

replace this line for mysql

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

upon

'engine' => null,

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

add a comment | 

4

As already specified we add to the AppServiceProvider.php in App/Providers

use IlluminateSupportFacadesSchema;  // add this



/**

 * Bootstrap any application services.

 *

 * @return void

 */

public function boot()

{

    Schema::defaultStringLength(191); // also this line

}

you can see more details in the link bellow (search for "Index Lengths & MySQL / MariaDB")
https://laravel.com/docs/5.5/migrations

BUT WELL THAT's not what I published all about! the thing is even when doing the above you will likely to get another error (that's when you run php artisan migrate command and because of the problem of the length, the operation will likely stuck in the middle. solution is below, and the user table is likely created without the rest or not totally correctly)
we need to roll back. the default roll back will not work. because the operation of migration didn't like finish. you need to delete the new created tables in the database manually.

we can do it using tinker as in below:

L:todos> php artisan tinker



Psy Shell v0.8.15 (PHP 7.1.10 — cli) by Justin Hileman



>>> Schema::drop('users')



=> null

I myself had a problem with users table.

after that you're good to go

php artisan migrate:rollback

php artisan migrate

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

add a comment | 

3

As outlined in the Migrations guide to fix this, all you have to do is edit your app/Providers/AppServiceProvider.php file and inside the boot method set a default string length:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migrations table.

To run all of your outstanding migrations, execute the migrate Artisan command:

php artisan migrate

After that everything should work as normal.

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

answered Jan 19 '18 at 5:43

user9162235

add a comment | 

3

Schema::defaultStringLength(191); will define the length of all strings 191 by default which may ruin your database. You must not go this way.

Just define the length of any specific column in the database migration class. For example, I'm defining the "name", "username" and "email" in the CreateUsersTable class as below:

public function up()

    {

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

            $table->increments('id');

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

            $table->string('username', 30)->unique();

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

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

share|improve this answer

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This is most preferable for me as I would rather not tweak any Laravel core codes.
  
  – Okiemute Omuta
  Jul 14 '18 at 2:41
  

  
  
  
  

add a comment | 

3

I am adding two sollution that work for me.

1st sollution is:

1. Open database.php file insde config dir/folder.


2. 
   

   Edit 'engine' => null, to 'engine' => 'InnoDB',

   
   
   

   This worked for me.

   
   

2nd sollution is:

1. 
   

   Open database.php file insde config dir/folder.
   
   2.Edit
   'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
   
   
   to
   

   
   
   

   'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',

   
   

Goodluck

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

add a comment | 

2

If you want to change in AppServiceProvider then you need to define the length of email field in migration. just replace the first line of code to the second line.

create_users_table

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

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

create_password_resets_table

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

$table->string('email', 50)->index();

After successfully changes you can run the migration.

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migration table.

share|improve this answer

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

add a comment | 

2

This is common since Laravel 5.4 changed the default database charater set to utf8mb4. What you have to do, is: edit your AppProviders.php by putting this code before the class declaration

use IlluminateSupportFacadesSchema;

Also, add this to the 'boot' function
Schema::defaultStringLength(191);

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

add a comment | 

2

update & insert these lines in app/Providers/AppServiceProvider.php

use IlluminateSupportFacadesSchema;  //insert this line

public function boot()

{

    Schema::defaultStringLength(191); //insert this line also

}

set your database engine in config/database.php in 'mysql' array

'engine' => 'InnoDB',

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

add a comment | 

2

I have just modified following line in users and password_resets migration file.

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

New : $table->string('email', 128)->unique();

Voila!!

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

add a comment | 

2

If you face this error while work on laravel while using command: php artisan migrate
then you just add 2 lines in the file: app->Providers->AppServiceProvider.php

1. use Schema;


2. Schema::defaultStringLength(191);

please check this image.
then run php artisan migrate command again.

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

add a comment | 

1

In order to avoid changing anything in your code, simply update your MySQL server to at least 5.7.7

Reference this for more info : https://laravel-news.com/laravel-5-4-key-too-long-error

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

add a comment | 

1

I think to force StringLenght to 191 is a really bad idea.
So I investigate to understand what is going on.

I noticed that this message error :

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key
was too long; max key length is 767 bytes

Started to show up after I updated my MySQL version. So I've checked the tables with PHPMyAdmin and I've noticed that all the new tables created were with the collation utf8mb4_unicode_ci instead of utf8_unicode_ci for the old ones.

In my doctrine config file, I noticed that charset was set to utf8mb4, but all my previous tables were created in utf8, so I guess this is some update magic that it start to work on utf8mb4.

Now the easy fix is to change the line charset in your ORM config file.
Then to drop the tables using utf8mb4_unicode_ci if you are in dev mode or fixe the charset if you can't drop them.

For Symfony 4

change charset: utf8mb4 to charset: utf8 in config/packages/doctrine.yaml

Now my doctrine migrations are working again just fine.

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks it's work for my ubuntu !
  
  – Crown Backend
  Jan 7 at 19:38
  

  
  
  
  

add a comment | 

1

The recommended solution is to enable innodb_large_prefix option of MySQL so you won't be getting into subsequent problems. And here is how to do that:

Open the my.ini MySQL configuration file and add the below lines under the [mysqld] line like this.

[mysqld]

innodb_file_format = Barracuda

innodb_large_prefix = 1

innodb_file_per_table = ON

After that, save your changes and restart your MySQL service.

Rollback if you need to and then re-run your migration.

---

Just in case your problem still persists, go to your database configuration file and set

'engine' => null, to 'engine' => 'innodb row_format=dynamic'

Hope it helps!

share|improve this answer

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

add a comment | 

1

1- Go to /config/database.php and find these lines

'mysql' => [

    ...,

    'charset' => 'utf8mb4',

    'collation' => 'utf8mb4_unicode_ci',

    ...,

    'engine' => null,

 ]

and change them to:

'mysql' => [

    ...,

    'charset' => 'utf8',

    'collation' => 'utf8_unicode_ci',

    ...,

    'engine' => 'InnoDB',

 ]

2- Run php artisan config:cache to reconfigure laravel

3- Delete the existing tables in your database and then run php artisan migrate again

share|improve this answer

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

add a comment | 

0

For anyone else who might run into this, my issue was that I was making a column of type string and trying to make it ->unsigned() when I meant for it to be an integer.

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

add a comment | 

0

The approached that work here was pass a second param with the key name (a short one):

$table->string('my_field_name')->unique(null,'key_name');

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

add a comment | 

0

In AppServiceProvider.php file:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

add a comment | 

-1

For me what worked was to update the dependencies by running.

composer update

You should also install the latest mysql version.

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42244541%2flaravel-migration-error-syntax-error-or-access-violation-1071-specified-key-wa%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

26 Answers
26

active

oldest

votes

26 Answers
26

active

oldest

votes

active

oldest

votes

active

oldest

votes

124

According to the official documentation, you can solve this quite easily.

Add following code to AppServiceProvider.php (/app/Providers/AppServiceProvider.php)

use IlluminateSupportFacadesSchema; //NEW: Import Schema



function boot()

{

    Schema::defaultStringLength(191); //NEW: Increase StringLength

}

MySQL reserves always the max amount for a UTF8 field which is 4 bytes so with 255 + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; you are over the 767 max key length limit. By @scaisedge

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.
  
  – shock_gone_wild
  Feb 16 '17 at 12:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…
  
  – absiddiqueLive
  Feb 17 '17 at 7:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.
  
  – shock_gone_wild
  Feb 17 '17 at 9:48
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  why exactly 191 characters @absiddiqueLive
  
  – PseudoAj
  Jun 15 '17 at 7:56
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  working on 5.7.0 . but why 191?
  
  – romal tandel
  Sep 5 '18 at 9:19
  

  
  
  
  

 | 
show 4 more comments

124

According to the official documentation, you can solve this quite easily.

Add following code to AppServiceProvider.php (/app/Providers/AppServiceProvider.php)

use IlluminateSupportFacadesSchema; //NEW: Import Schema



function boot()

{

    Schema::defaultStringLength(191); //NEW: Increase StringLength

}

MySQL reserves always the max amount for a UTF8 field which is 4 bytes so with 255 + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; you are over the 767 max key length limit. By @scaisedge

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.
  
  – shock_gone_wild
  Feb 16 '17 at 12:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…
  
  – absiddiqueLive
  Feb 17 '17 at 7:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.
  
  – shock_gone_wild
  Feb 17 '17 at 9:48
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  why exactly 191 characters @absiddiqueLive
  
  – PseudoAj
  Jun 15 '17 at 7:56
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  working on 5.7.0 . but why 191?
  
  – romal tandel
  Sep 5 '18 at 9:19
  

  
  
  
  

 | 
show 4 more comments

124

124

124

According to the official documentation, you can solve this quite easily.

Add following code to AppServiceProvider.php (/app/Providers/AppServiceProvider.php)

use IlluminateSupportFacadesSchema; //NEW: Import Schema



function boot()

{

    Schema::defaultStringLength(191); //NEW: Increase StringLength

}

MySQL reserves always the max amount for a UTF8 field which is 4 bytes so with 255 + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; you are over the 767 max key length limit. By @scaisedge

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

According to the official documentation, you can solve this quite easily.

Add following code to AppServiceProvider.php (/app/Providers/AppServiceProvider.php)

use IlluminateSupportFacadesSchema; //NEW: Import Schema



function boot()

{

    Schema::defaultStringLength(191); //NEW: Increase StringLength

}

MySQL reserves always the max amount for a UTF8 field which is 4 bytes so with 255 + 255 with your DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; you are over the 767 max key length limit. By @scaisedge

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

share|improve this answer

share|improve this answer

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

edited Feb 19 at 20:26

Chuck Le Butt

28.4k46151229

28.4k46151229

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

answered Feb 15 '17 at 9:52

absiddiqueLiveabsiddiqueLive

3,53821327

3,53821327

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.
  
  – shock_gone_wild
  Feb 16 '17 at 12:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…
  
  – absiddiqueLive
  Feb 17 '17 at 7:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.
  
  – shock_gone_wild
  Feb 17 '17 at 9:48
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  why exactly 191 characters @absiddiqueLive
  
  – PseudoAj
  Jun 15 '17 at 7:56
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  working on 5.7.0 . but why 191?
  
  – romal tandel
  Sep 5 '18 at 9:19
  

  
  
  
  

 | 
show 4 more comments

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.
  
  – shock_gone_wild
  Feb 16 '17 at 12:30
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…
  
  – absiddiqueLive
  Feb 17 '17 at 7:47
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.
  
  – shock_gone_wild
  Feb 17 '17 at 9:48
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  why exactly 191 characters @absiddiqueLive
  
  – PseudoAj
  Jun 15 '17 at 7:56
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  working on 5.7.0 . but why 191?
  
  – romal tandel
  Sep 5 '18 at 9:19
  

  
  
  
  

1

1

Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.

– shock_gone_wild
Feb 16 '17 at 12:30

Be careful about this solution. If you index email fields for example, stored emails can only have a max length of 191 chars. This is less than the official RFC states.

– shock_gone_wild
Feb 16 '17 at 12:30

1

1

This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…

– absiddiqueLive
Feb 17 '17 at 7:47

This solution suggest by Laravel github.com/laravel/framework/issues/17508 laracasts.com/discuss/channels/laravel/…

– absiddiqueLive
Feb 17 '17 at 7:47

It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.

– shock_gone_wild
Feb 17 '17 at 9:48

It is working and is a valid solution, but I just wanted to point out, that there are possible pitfalls using this approach.

– shock_gone_wild
Feb 17 '17 at 9:48

2

2

why exactly 191 characters @absiddiqueLive

– PseudoAj
Jun 15 '17 at 7:56

why exactly 191 characters @absiddiqueLive

– PseudoAj
Jun 15 '17 at 7:56

2

2

working on 5.7.0 . but why 191?

– romal tandel
Sep 5 '18 at 9:19

working on 5.7.0 . but why 191?

– romal tandel
Sep 5 '18 at 9:19

 | 
show 4 more comments

59

I don't know why the above solution and the official solution which is adding

Schema::defaultStringLength(191);

in AppServiceProvider didn't work for me.
What worked for was editing the database.php file in config folder.
Just edit

'charset' => 'utf8mb4',

'collation' => 'utf8mb4_unicode_ci',

to

'charset' => 'utf8',

'collation' => 'utf8_unicode_ci',

and it should work.
Hope it helps.

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593
  
  – Jeff Puckett
  Sep 27 '17 at 19:01
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thankyou really help..
  
  – Stefen Wiranata
  Mar 29 '18 at 9:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Still not worked! Any idea??
  
  – Hiren Gohel
  Apr 25 '18 at 11:37
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I think you missed this part use IlluminateSupportFacadesSchema; at the top.
  
  – pimpace
  Aug 18 '18 at 19:53
  
  
  

  
  
  
  

add a comment | 

59

I don't know why the above solution and the official solution which is adding

Schema::defaultStringLength(191);

in AppServiceProvider didn't work for me.
What worked for was editing the database.php file in config folder.
Just edit

'charset' => 'utf8mb4',

'collation' => 'utf8mb4_unicode_ci',

to

'charset' => 'utf8',

'collation' => 'utf8_unicode_ci',

and it should work.
Hope it helps.

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593
  
  – Jeff Puckett
  Sep 27 '17 at 19:01
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thankyou really help..
  
  – Stefen Wiranata
  Mar 29 '18 at 9:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Still not worked! Any idea??
  
  – Hiren Gohel
  Apr 25 '18 at 11:37
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I think you missed this part use IlluminateSupportFacadesSchema; at the top.
  
  – pimpace
  Aug 18 '18 at 19:53
  
  
  

  
  
  
  

add a comment | 

59

59

59

I don't know why the above solution and the official solution which is adding

Schema::defaultStringLength(191);

in AppServiceProvider didn't work for me.
What worked for was editing the database.php file in config folder.
Just edit

'charset' => 'utf8mb4',

'collation' => 'utf8mb4_unicode_ci',

to

'charset' => 'utf8',

'collation' => 'utf8_unicode_ci',

and it should work.
Hope it helps.

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

I don't know why the above solution and the official solution which is adding

Schema::defaultStringLength(191);

in AppServiceProvider didn't work for me.
What worked for was editing the database.php file in config folder.
Just edit

'charset' => 'utf8mb4',

'collation' => 'utf8mb4_unicode_ci',

to

'charset' => 'utf8',

'collation' => 'utf8_unicode_ci',

and it should work.
Hope it helps.

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

share|improve this answer

share|improve this answer

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

answered Sep 17 '17 at 8:29

Koushik DasKoushik Das

2,1321720

2,1321720

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593
  
  – Jeff Puckett
  Sep 27 '17 at 19:01
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thankyou really help..
  
  – Stefen Wiranata
  Mar 29 '18 at 9:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Still not worked! Any idea??
  
  – Hiren Gohel
  Apr 25 '18 at 11:37
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I think you missed this part use IlluminateSupportFacadesSchema; at the top.
  
  – pimpace
  Aug 18 '18 at 19:53
  
  
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593
  
  – Jeff Puckett
  Sep 27 '17 at 19:01
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  thankyou really help..
  
  – Stefen Wiranata
  Mar 29 '18 at 9:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Still not worked! Any idea??
  
  – Hiren Gohel
  Apr 25 '18 at 11:37
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I think you missed this part use IlluminateSupportFacadesSchema; at the top.
  
  – pimpace
  Aug 18 '18 at 19:53
  
  
  

  
  
  
  

1

1

Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593

– Jeff Puckett
Sep 27 '17 at 19:01

Using this character set will only allow you to save Standard ASCII, and not multibyte special characters like those from Arabic, Hebrew, most European scripts, and of course emoji. see also stackoverflow.com/a/15128103/4233593

– Jeff Puckett
Sep 27 '17 at 19:01

thankyou really help..

– Stefen Wiranata
Mar 29 '18 at 9:05

thankyou really help..

– Stefen Wiranata
Mar 29 '18 at 9:05

Still not worked! Any idea??

– Hiren Gohel
Apr 25 '18 at 11:37

Still not worked! Any idea??

– Hiren Gohel
Apr 25 '18 at 11:37

1

1

I think you missed this part use IlluminateSupportFacadesSchema; at the top.

– pimpace
Aug 18 '18 at 19:53

I think you missed this part use IlluminateSupportFacadesSchema; at the top.

– pimpace
Aug 18 '18 at 19:53

add a comment | 

32

I'm just adding this answer here as it's the quickest solution for me. Just set the default database engine to 'InnoDB' on

/config/database.php

'mysql' => [

    ...,

    ...,

    'engine' => 'InnoDB',

 ]

then run php artisan config:cache to clear and refresh the configuration cache

share|improve this answer

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Works perfect thank you.
  
  – PHPFan
  Oct 25 '18 at 21:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  changing engine from null to InnoDB worked
  
  – merdan
  Dec 13 '18 at 12:43
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  This should be marked as the best solution
  
  – Hazem Emad
  Jan 29 at 11:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This should be the accepted solution - Thanks
  
  – Tricky
  Feb 26 at 13:49
  

  
  
  
  

add a comment | 

32

I'm just adding this answer here as it's the quickest solution for me. Just set the default database engine to 'InnoDB' on

/config/database.php

'mysql' => [

    ...,

    ...,

    'engine' => 'InnoDB',

 ]

then run php artisan config:cache to clear and refresh the configuration cache

share|improve this answer

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Works perfect thank you.
  
  – PHPFan
  Oct 25 '18 at 21:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  changing engine from null to InnoDB worked
  
  – merdan
  Dec 13 '18 at 12:43
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  This should be marked as the best solution
  
  – Hazem Emad
  Jan 29 at 11:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This should be the accepted solution - Thanks
  
  – Tricky
  Feb 26 at 13:49
  

  
  
  
  

add a comment | 

32

32

32

I'm just adding this answer here as it's the quickest solution for me. Just set the default database engine to 'InnoDB' on

/config/database.php

'mysql' => [

    ...,

    ...,

    'engine' => 'InnoDB',

 ]

then run php artisan config:cache to clear and refresh the configuration cache

share|improve this answer

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

I'm just adding this answer here as it's the quickest solution for me. Just set the default database engine to 'InnoDB' on

/config/database.php

'mysql' => [

    ...,

    ...,

    'engine' => 'InnoDB',

 ]

then run php artisan config:cache to clear and refresh the configuration cache

share|improve this answer

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

share|improve this answer

share|improve this answer

edited Dec 21 '18 at 13:12

edited Dec 21 '18 at 13:12

edited Dec 21 '18 at 13:12

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

answered Oct 9 '17 at 7:50

Dexter BengilDexter Bengil

2,35332236

2,35332236

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Works perfect thank you.
  
  – PHPFan
  Oct 25 '18 at 21:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  changing engine from null to InnoDB worked
  
  – merdan
  Dec 13 '18 at 12:43
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  This should be marked as the best solution
  
  – Hazem Emad
  Jan 29 at 11:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This should be the accepted solution - Thanks
  
  – Tricky
  Feb 26 at 13:49
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Works perfect thank you.
  
  – PHPFan
  Oct 25 '18 at 21:14
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  changing engine from null to InnoDB worked
  
  – merdan
  Dec 13 '18 at 12:43
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  This should be marked as the best solution
  
  – Hazem Emad
  Jan 29 at 11:28
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This should be the accepted solution - Thanks
  
  – Tricky
  Feb 26 at 13:49
  

  
  
  
  

2

2

Works perfect thank you.

– PHPFan
Oct 25 '18 at 21:14

Works perfect thank you.

– PHPFan
Oct 25 '18 at 21:14

1

1

changing engine from null to InnoDB worked

– merdan
Dec 13 '18 at 12:43

changing engine from null to InnoDB worked

– merdan
Dec 13 '18 at 12:43

2

2

This should be marked as the best solution

– Hazem Emad
Jan 29 at 11:28

This should be marked as the best solution

– Hazem Emad
Jan 29 at 11:28

This should be the accepted solution - Thanks

– Tricky
Feb 26 at 13:49

This should be the accepted solution - Thanks

– Tricky
Feb 26 at 13:49

add a comment | 

21

In the AppServiceProvider.php,you include this code top of the file.

use IlluminateSupportFacadesSchema;

And you add this code in boot method.

 Schema::defaultStringLength(191);

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

add a comment | 

21

In the AppServiceProvider.php,you include this code top of the file.

use IlluminateSupportFacadesSchema;

And you add this code in boot method.

 Schema::defaultStringLength(191);

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

add a comment | 

21

21

21

In the AppServiceProvider.php,you include this code top of the file.

use IlluminateSupportFacadesSchema;

And you add this code in boot method.

 Schema::defaultStringLength(191);

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

In the AppServiceProvider.php,you include this code top of the file.

use IlluminateSupportFacadesSchema;

And you add this code in boot method.

 Schema::defaultStringLength(191);

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

share|improve this answer

share|improve this answer

edited Apr 22 '17 at 22:00

zheek

66711020

edited Apr 22 '17 at 22:00

zheek

66711020

edited Apr 22 '17 at 22:00

zheek

66711020

66711020

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

answered Mar 10 '17 at 4:02

user7688086user7688086

21113

21113

add a comment | 

add a comment | 

17

This issue is caused in Laravel 5.4 by the database version.

According to the docs (in the Index Lengths & MySQL / MariaDB section):

Laravel uses the utf8mb4 character set by default, which includes
support for storing "emojis" in the database. If you are running a
version of MySQL older than the 5.7.7 release or MariaDB older than
the 10.2.2 release, you may need to manually configure the default
string length generated by migrations in order for MySQL to create
indexes for them. You may configure this by calling the
Schema::defaultStringLength method within your AppServiceProvider.

In other words, in <ROOT>/app/Providers/AppServiceProvider.php:

// Import Schema

use IlluminateSupportFacadesSchema;

// ...



class AppServiceProvider extends ServiceProvider

{



public function boot()

{

    // Add the following line

    Schema::defaultStringLength(191);

}



// ...



}

But as the comment on the other answer says:

Be careful about this solution. If you index email fields for example,
stored emails can only have a max length of 191 chars. This is less
than the official RFC states.

So the documentation also proposes another solution:

Alternatively, you may enable the innodb_large_prefix option for your
database. Refer to your database's documentation for instructions on
how to properly enable this option.

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

add a comment | 

17

This issue is caused in Laravel 5.4 by the database version.

According to the docs (in the Index Lengths & MySQL / MariaDB section):

Laravel uses the utf8mb4 character set by default, which includes
support for storing "emojis" in the database. If you are running a
version of MySQL older than the 5.7.7 release or MariaDB older than
the 10.2.2 release, you may need to manually configure the default
string length generated by migrations in order for MySQL to create
indexes for them. You may configure this by calling the
Schema::defaultStringLength method within your AppServiceProvider.

In other words, in <ROOT>/app/Providers/AppServiceProvider.php:

// Import Schema

use IlluminateSupportFacadesSchema;

// ...



class AppServiceProvider extends ServiceProvider

{



public function boot()

{

    // Add the following line

    Schema::defaultStringLength(191);

}



// ...



}

But as the comment on the other answer says:

Be careful about this solution. If you index email fields for example,
stored emails can only have a max length of 191 chars. This is less
than the official RFC states.

So the documentation also proposes another solution:

Alternatively, you may enable the innodb_large_prefix option for your
database. Refer to your database's documentation for instructions on
how to properly enable this option.

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

add a comment | 

17

17

17

This issue is caused in Laravel 5.4 by the database version.

According to the docs (in the Index Lengths & MySQL / MariaDB section):

Laravel uses the utf8mb4 character set by default, which includes
support for storing "emojis" in the database. If you are running a
version of MySQL older than the 5.7.7 release or MariaDB older than
the 10.2.2 release, you may need to manually configure the default
string length generated by migrations in order for MySQL to create
indexes for them. You may configure this by calling the
Schema::defaultStringLength method within your AppServiceProvider.

In other words, in <ROOT>/app/Providers/AppServiceProvider.php:

// Import Schema

use IlluminateSupportFacadesSchema;

// ...



class AppServiceProvider extends ServiceProvider

{



public function boot()

{

    // Add the following line

    Schema::defaultStringLength(191);

}



// ...



}

But as the comment on the other answer says:

Be careful about this solution. If you index email fields for example,
stored emails can only have a max length of 191 chars. This is less
than the official RFC states.

So the documentation also proposes another solution:

Alternatively, you may enable the innodb_large_prefix option for your
database. Refer to your database's documentation for instructions on
how to properly enable this option.

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

This issue is caused in Laravel 5.4 by the database version.

According to the docs (in the Index Lengths & MySQL / MariaDB section):

Laravel uses the utf8mb4 character set by default, which includes
support for storing "emojis" in the database. If you are running a
version of MySQL older than the 5.7.7 release or MariaDB older than
the 10.2.2 release, you may need to manually configure the default
string length generated by migrations in order for MySQL to create
indexes for them. You may configure this by calling the
Schema::defaultStringLength method within your AppServiceProvider.

In other words, in <ROOT>/app/Providers/AppServiceProvider.php:

// Import Schema

use IlluminateSupportFacadesSchema;

// ...



class AppServiceProvider extends ServiceProvider

{



public function boot()

{

    // Add the following line

    Schema::defaultStringLength(191);

}



// ...



}

But as the comment on the other answer says:

Be careful about this solution. If you index email fields for example,
stored emails can only have a max length of 191 chars. This is less
than the official RFC states.

So the documentation also proposes another solution:

Alternatively, you may enable the innodb_large_prefix option for your
database. Refer to your database's documentation for instructions on
how to properly enable this option.

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

share|improve this answer

share|improve this answer

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

answered Feb 20 '17 at 19:39

Esteban HerreraEsteban Herrera

1,66511227

1,66511227

add a comment | 

add a comment | 

12

For someone who don't want to change AppServiceProvider.php.
(In my opinion, it's bad idea to change AppServiceProvider.php just for migration)

You can add back the data length to the migration file under database/migrations/ as below:

create_users_table.php

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

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

create_password_resets_table.php

$table->string('email',128)->index();

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This can be a problem since emails can be up to 255(ish) characters
  
  – Half Crazed
  Jun 18 '17 at 1:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272
  
  – helloroy
  Jun 19 '17 at 1:17
  

  
  
  
  

add a comment | 

12

For someone who don't want to change AppServiceProvider.php.
(In my opinion, it's bad idea to change AppServiceProvider.php just for migration)

You can add back the data length to the migration file under database/migrations/ as below:

create_users_table.php

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

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

create_password_resets_table.php

$table->string('email',128)->index();

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This can be a problem since emails can be up to 255(ish) characters
  
  – Half Crazed
  Jun 18 '17 at 1:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272
  
  – helloroy
  Jun 19 '17 at 1:17
  

  
  
  
  

add a comment | 

12

12

12

For someone who don't want to change AppServiceProvider.php.
(In my opinion, it's bad idea to change AppServiceProvider.php just for migration)

You can add back the data length to the migration file under database/migrations/ as below:

create_users_table.php

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

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

create_password_resets_table.php

$table->string('email',128)->index();

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

For someone who don't want to change AppServiceProvider.php.
(In my opinion, it's bad idea to change AppServiceProvider.php just for migration)

You can add back the data length to the migration file under database/migrations/ as below:

create_users_table.php

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

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

create_password_resets_table.php

$table->string('email',128)->index();

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

share|improve this answer

share|improve this answer

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

edited Oct 26 '18 at 8:42

Dexter Bengil

2,35332236

2,35332236

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

answered Apr 21 '17 at 16:46

helloroyhelloroy

16814

16814

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This can be a problem since emails can be up to 255(ish) characters
  
  – Half Crazed
  Jun 18 '17 at 1:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272
  
  – helloroy
  Jun 19 '17 at 1:17
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This can be a problem since emails can be up to 255(ish) characters
  
  – Half Crazed
  Jun 18 '17 at 1:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272
  
  – helloroy
  Jun 19 '17 at 1:17
  

  
  
  
  

This can be a problem since emails can be up to 255(ish) characters

– Half Crazed
Jun 18 '17 at 1:02

This can be a problem since emails can be up to 255(ish) characters

– Half Crazed
Jun 18 '17 at 1:02

You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272

– helloroy
Jun 19 '17 at 1:17

You are right @HalfCrazed, but I suggest this answer stackoverflow.com/questions/1297272

– helloroy
Jun 19 '17 at 1:17

add a comment | 

6

I have solved this issue and edited my config->database.php file to like my database ('charset'=>'utf8') and the ('collation'=>'utf8_general_ci'), so my problem is solved the code as follow:

'mysql' => [

        'driver' => 'mysql',

        'host' => env('DB_HOST', '127.0.0.1'),

        'port' => env('DB_PORT', '3306'),

        'database' => env('DB_DATABASE', 'forge'),

        'username' => env('DB_USERNAME', 'forge'),

        'password' => env('DB_PASSWORD', ''),

        'unix_socket' => env('DB_SOCKET', ''),

        'charset' => 'utf8',

        'collation' => 'utf8_general_ci',

        'prefix' => '',

        'strict' => true,

        'engine' => null,

    ],

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

add a comment | 

6

I have solved this issue and edited my config->database.php file to like my database ('charset'=>'utf8') and the ('collation'=>'utf8_general_ci'), so my problem is solved the code as follow:

'mysql' => [

        'driver' => 'mysql',

        'host' => env('DB_HOST', '127.0.0.1'),

        'port' => env('DB_PORT', '3306'),

        'database' => env('DB_DATABASE', 'forge'),

        'username' => env('DB_USERNAME', 'forge'),

        'password' => env('DB_PASSWORD', ''),

        'unix_socket' => env('DB_SOCKET', ''),

        'charset' => 'utf8',

        'collation' => 'utf8_general_ci',

        'prefix' => '',

        'strict' => true,

        'engine' => null,

    ],

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

add a comment | 

6

6

6

I have solved this issue and edited my config->database.php file to like my database ('charset'=>'utf8') and the ('collation'=>'utf8_general_ci'), so my problem is solved the code as follow:

'mysql' => [

        'driver' => 'mysql',

        'host' => env('DB_HOST', '127.0.0.1'),

        'port' => env('DB_PORT', '3306'),

        'database' => env('DB_DATABASE', 'forge'),

        'username' => env('DB_USERNAME', 'forge'),

        'password' => env('DB_PASSWORD', ''),

        'unix_socket' => env('DB_SOCKET', ''),

        'charset' => 'utf8',

        'collation' => 'utf8_general_ci',

        'prefix' => '',

        'strict' => true,

        'engine' => null,

    ],

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

I have solved this issue and edited my config->database.php file to like my database ('charset'=>'utf8') and the ('collation'=>'utf8_general_ci'), so my problem is solved the code as follow:

'mysql' => [

        'driver' => 'mysql',

        'host' => env('DB_HOST', '127.0.0.1'),

        'port' => env('DB_PORT', '3306'),

        'database' => env('DB_DATABASE', 'forge'),

        'username' => env('DB_USERNAME', 'forge'),

        'password' => env('DB_PASSWORD', ''),

        'unix_socket' => env('DB_SOCKET', ''),

        'charset' => 'utf8',

        'collation' => 'utf8_general_ci',

        'prefix' => '',

        'strict' => true,

        'engine' => null,

    ],

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

share|improve this answer

share|improve this answer

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

answered Apr 20 '18 at 6:24

Ahmad ShakibAhmad Shakib

30736

30736

add a comment | 

add a comment | 

6

Add the below code in app/Providers/AppServiceProvider.php method:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

first you have to delete (if you have) users table,
password_resets table from the database and delete users and password_resets entries from migrations table and then after deleting old tables run php artisan migrate command

share|improve this answer

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

add a comment | 

6

Add the below code in app/Providers/AppServiceProvider.php method:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

first you have to delete (if you have) users table,
password_resets table from the database and delete users and password_resets entries from migrations table and then after deleting old tables run php artisan migrate command

share|improve this answer

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

add a comment | 

6

6

6

Add the below code in app/Providers/AppServiceProvider.php method:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

first you have to delete (if you have) users table,
password_resets table from the database and delete users and password_resets entries from migrations table and then after deleting old tables run php artisan migrate command

share|improve this answer

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

Add the below code in app/Providers/AppServiceProvider.php method:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

first you have to delete (if you have) users table,
password_resets table from the database and delete users and password_resets entries from migrations table and then after deleting old tables run php artisan migrate command

share|improve this answer

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

share|improve this answer

share|improve this answer

edited Dec 16 '18 at 12:20

edited Dec 16 '18 at 12:20

edited Dec 16 '18 at 12:20

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

answered Feb 8 '18 at 6:37

Udhav SarvaiyaUdhav Sarvaiya

2,34071930

2,34071930

add a comment | 

add a comment | 

5

Instead of setting a limit on length I would propose the following, which has worked for me.

Inside

config/database.php

replace this line for mysql

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

upon

'engine' => null,

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

add a comment | 

5

Instead of setting a limit on length I would propose the following, which has worked for me.

Inside

config/database.php

replace this line for mysql

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

upon

'engine' => null,

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

add a comment | 

5

5

5

Instead of setting a limit on length I would propose the following, which has worked for me.

Inside

config/database.php

replace this line for mysql

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

upon

'engine' => null,

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

Instead of setting a limit on length I would propose the following, which has worked for me.

Inside

config/database.php

replace this line for mysql

'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

upon

'engine' => null,

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

share|improve this answer

share|improve this answer

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

edited Mar 19 '18 at 13:36

Derrick Moeller

2,79021433

2,79021433

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

answered Jul 24 '17 at 20:21

Md. Noor-A-Alam SiddiqueMd. Noor-A-Alam Siddique

61169

61169

add a comment | 

add a comment | 

4

As already specified we add to the AppServiceProvider.php in App/Providers

use IlluminateSupportFacadesSchema;  // add this



/**

 * Bootstrap any application services.

 *

 * @return void

 */

public function boot()

{

    Schema::defaultStringLength(191); // also this line

}

you can see more details in the link bellow (search for "Index Lengths & MySQL / MariaDB")
https://laravel.com/docs/5.5/migrations

BUT WELL THAT's not what I published all about! the thing is even when doing the above you will likely to get another error (that's when you run php artisan migrate command and because of the problem of the length, the operation will likely stuck in the middle. solution is below, and the user table is likely created without the rest or not totally correctly)
we need to roll back. the default roll back will not work. because the operation of migration didn't like finish. you need to delete the new created tables in the database manually.

we can do it using tinker as in below:

L:todos> php artisan tinker



Psy Shell v0.8.15 (PHP 7.1.10 — cli) by Justin Hileman



>>> Schema::drop('users')



=> null

I myself had a problem with users table.

after that you're good to go

php artisan migrate:rollback

php artisan migrate

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

add a comment | 

4

As already specified we add to the AppServiceProvider.php in App/Providers

use IlluminateSupportFacadesSchema;  // add this



/**

 * Bootstrap any application services.

 *

 * @return void

 */

public function boot()

{

    Schema::defaultStringLength(191); // also this line

}

you can see more details in the link bellow (search for "Index Lengths & MySQL / MariaDB")
https://laravel.com/docs/5.5/migrations

BUT WELL THAT's not what I published all about! the thing is even when doing the above you will likely to get another error (that's when you run php artisan migrate command and because of the problem of the length, the operation will likely stuck in the middle. solution is below, and the user table is likely created without the rest or not totally correctly)
we need to roll back. the default roll back will not work. because the operation of migration didn't like finish. you need to delete the new created tables in the database manually.

we can do it using tinker as in below:

L:todos> php artisan tinker



Psy Shell v0.8.15 (PHP 7.1.10 — cli) by Justin Hileman



>>> Schema::drop('users')



=> null

I myself had a problem with users table.

after that you're good to go

php artisan migrate:rollback

php artisan migrate

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

add a comment | 

4

4

4

As already specified we add to the AppServiceProvider.php in App/Providers

use IlluminateSupportFacadesSchema;  // add this



/**

 * Bootstrap any application services.

 *

 * @return void

 */

public function boot()

{

    Schema::defaultStringLength(191); // also this line

}

you can see more details in the link bellow (search for "Index Lengths & MySQL / MariaDB")
https://laravel.com/docs/5.5/migrations

BUT WELL THAT's not what I published all about! the thing is even when doing the above you will likely to get another error (that's when you run php artisan migrate command and because of the problem of the length, the operation will likely stuck in the middle. solution is below, and the user table is likely created without the rest or not totally correctly)
we need to roll back. the default roll back will not work. because the operation of migration didn't like finish. you need to delete the new created tables in the database manually.

we can do it using tinker as in below:

L:todos> php artisan tinker



Psy Shell v0.8.15 (PHP 7.1.10 — cli) by Justin Hileman



>>> Schema::drop('users')



=> null

I myself had a problem with users table.

after that you're good to go

php artisan migrate:rollback

php artisan migrate

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

As already specified we add to the AppServiceProvider.php in App/Providers

use IlluminateSupportFacadesSchema;  // add this



/**

 * Bootstrap any application services.

 *

 * @return void

 */

public function boot()

{

    Schema::defaultStringLength(191); // also this line

}

you can see more details in the link bellow (search for "Index Lengths & MySQL / MariaDB")
https://laravel.com/docs/5.5/migrations

BUT WELL THAT's not what I published all about! the thing is even when doing the above you will likely to get another error (that's when you run php artisan migrate command and because of the problem of the length, the operation will likely stuck in the middle. solution is below, and the user table is likely created without the rest or not totally correctly)
we need to roll back. the default roll back will not work. because the operation of migration didn't like finish. you need to delete the new created tables in the database manually.

we can do it using tinker as in below:

L:todos> php artisan tinker



Psy Shell v0.8.15 (PHP 7.1.10 — cli) by Justin Hileman



>>> Schema::drop('users')



=> null

I myself had a problem with users table.

after that you're good to go

php artisan migrate:rollback

php artisan migrate

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

share|improve this answer

share|improve this answer

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

edited Aug 16 '18 at 8:01

Dexter Bengil

2,35332236

2,35332236

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

answered Jan 17 '18 at 20:37

Mohamed AllalMohamed Allal

2,4391621

2,4391621

add a comment | 

add a comment | 

3

As outlined in the Migrations guide to fix this, all you have to do is edit your app/Providers/AppServiceProvider.php file and inside the boot method set a default string length:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migrations table.

To run all of your outstanding migrations, execute the migrate Artisan command:

php artisan migrate

After that everything should work as normal.

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

answered Jan 19 '18 at 5:43

user9162235

add a comment | 

3

As outlined in the Migrations guide to fix this, all you have to do is edit your app/Providers/AppServiceProvider.php file and inside the boot method set a default string length:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migrations table.

To run all of your outstanding migrations, execute the migrate Artisan command:

php artisan migrate

After that everything should work as normal.

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

answered Jan 19 '18 at 5:43

user9162235

add a comment | 

3

3

3

As outlined in the Migrations guide to fix this, all you have to do is edit your app/Providers/AppServiceProvider.php file and inside the boot method set a default string length:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migrations table.

To run all of your outstanding migrations, execute the migrate Artisan command:

php artisan migrate

After that everything should work as normal.

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

answered Jan 19 '18 at 5:43

user9162235

As outlined in the Migrations guide to fix this, all you have to do is edit your app/Providers/AppServiceProvider.php file and inside the boot method set a default string length:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migrations table.

To run all of your outstanding migrations, execute the migrate Artisan command:

php artisan migrate

After that everything should work as normal.

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

answered Jan 19 '18 at 5:43

user9162235

share|improve this answer

share|improve this answer

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

edited Mar 19 '18 at 18:54

Dexter Bengil

2,35332236

2,35332236

answered Jan 19 '18 at 5:43

user9162235

answered Jan 19 '18 at 5:43

user9162235

answered Jan 19 '18 at 5:43

user9162235

add a comment | 

add a comment | 

3

Schema::defaultStringLength(191); will define the length of all strings 191 by default which may ruin your database. You must not go this way.

Just define the length of any specific column in the database migration class. For example, I'm defining the "name", "username" and "email" in the CreateUsersTable class as below:

public function up()

    {

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

            $table->increments('id');

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

            $table->string('username', 30)->unique();

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

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

share|improve this answer

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This is most preferable for me as I would rather not tweak any Laravel core codes.
  
  – Okiemute Omuta
  Jul 14 '18 at 2:41
  

  
  
  
  

add a comment | 

3

Schema::defaultStringLength(191); will define the length of all strings 191 by default which may ruin your database. You must not go this way.

Just define the length of any specific column in the database migration class. For example, I'm defining the "name", "username" and "email" in the CreateUsersTable class as below:

public function up()

    {

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

            $table->increments('id');

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

            $table->string('username', 30)->unique();

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

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

share|improve this answer

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This is most preferable for me as I would rather not tweak any Laravel core codes.
  
  – Okiemute Omuta
  Jul 14 '18 at 2:41
  

  
  
  
  

add a comment | 

3

3

3

Schema::defaultStringLength(191); will define the length of all strings 191 by default which may ruin your database. You must not go this way.

Just define the length of any specific column in the database migration class. For example, I'm defining the "name", "username" and "email" in the CreateUsersTable class as below:

public function up()

    {

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

            $table->increments('id');

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

            $table->string('username', 30)->unique();

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

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

share|improve this answer

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

Schema::defaultStringLength(191); will define the length of all strings 191 by default which may ruin your database. You must not go this way.

Just define the length of any specific column in the database migration class. For example, I'm defining the "name", "username" and "email" in the CreateUsersTable class as below:

public function up()

    {

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

            $table->increments('id');

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

            $table->string('username', 30)->unique();

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

            $table->string('password');

            $table->rememberToken();

            $table->timestamps();

        });

    }

share|improve this answer

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

share|improve this answer

share|improve this answer

edited Apr 23 '18 at 9:20

edited Apr 23 '18 at 9:20

edited Apr 23 '18 at 9:20

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

answered Apr 23 '18 at 9:08

Fatema T. ZuhoraFatema T. Zuhora

9711

9711

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This is most preferable for me as I would rather not tweak any Laravel core codes.
  
  – Okiemute Omuta
  Jul 14 '18 at 2:41
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This is most preferable for me as I would rather not tweak any Laravel core codes.
  
  – Okiemute Omuta
  Jul 14 '18 at 2:41
  

  
  
  
  

1

1

This is most preferable for me as I would rather not tweak any Laravel core codes.

– Okiemute Omuta
Jul 14 '18 at 2:41

This is most preferable for me as I would rather not tweak any Laravel core codes.

– Okiemute Omuta
Jul 14 '18 at 2:41

add a comment | 

3

I am adding two sollution that work for me.

1st sollution is:

1. Open database.php file insde config dir/folder.


2. 
   

   Edit 'engine' => null, to 'engine' => 'InnoDB',

   
   
   

   This worked for me.

   
   

2nd sollution is:

1. 
   

   Open database.php file insde config dir/folder.
   
   2.Edit
   'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
   
   
   to
   

   
   
   

   'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',

   
   

Goodluck

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

add a comment | 

3

I am adding two sollution that work for me.

1st sollution is:

1. Open database.php file insde config dir/folder.


2. 
   

   Edit 'engine' => null, to 'engine' => 'InnoDB',

   
   
   

   This worked for me.

   
   

2nd sollution is:

1. 
   

   Open database.php file insde config dir/folder.
   
   2.Edit
   'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
   
   
   to
   

   
   
   

   'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',

   
   

Goodluck

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

add a comment | 

3

3

3

I am adding two sollution that work for me.

1st sollution is:

1. Open database.php file insde config dir/folder.


2. 
   

   Edit 'engine' => null, to 'engine' => 'InnoDB',

   
   
   

   This worked for me.

   
   

2nd sollution is:

1. 
   

   Open database.php file insde config dir/folder.
   
   2.Edit
   'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
   
   
   to
   

   
   
   

   'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',

   
   

Goodluck

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

I am adding two sollution that work for me.

1st sollution is:

1. Open database.php file insde config dir/folder.


2. 
   

   Edit 'engine' => null, to 'engine' => 'InnoDB',

   
   
   

   This worked for me.

   
   

2nd sollution is:

1. 
   

   Open database.php file insde config dir/folder.
   
   2.Edit
   'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
   
   
   to
   

   
   
   

   'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',

   
   

Goodluck

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

share|improve this answer

share|improve this answer

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

answered Jun 28 '18 at 13:33

Arslan AhmadArslan Ahmad

840820

840820

add a comment | 

add a comment | 

2

If you want to change in AppServiceProvider then you need to define the length of email field in migration. just replace the first line of code to the second line.

create_users_table

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

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

create_password_resets_table

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

$table->string('email', 50)->index();

After successfully changes you can run the migration.

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migration table.

share|improve this answer

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

add a comment | 

2

If you want to change in AppServiceProvider then you need to define the length of email field in migration. just replace the first line of code to the second line.

create_users_table

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

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

create_password_resets_table

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

$table->string('email', 50)->index();

After successfully changes you can run the migration.

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migration table.

share|improve this answer

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

add a comment | 

2

2

2

If you want to change in AppServiceProvider then you need to define the length of email field in migration. just replace the first line of code to the second line.

create_users_table

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

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

create_password_resets_table

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

$table->string('email', 50)->index();

After successfully changes you can run the migration.

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migration table.

share|improve this answer

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

If you want to change in AppServiceProvider then you need to define the length of email field in migration. just replace the first line of code to the second line.

create_users_table

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

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

create_password_resets_table

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

$table->string('email', 50)->index();

After successfully changes you can run the migration.

Note: first you have to delete (if you have) users table, password_resets table from the database and delete users and password_resets entries from migration table.

share|improve this answer

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

share|improve this answer

share|improve this answer

edited Jun 25 '17 at 8:16

edited Jun 25 '17 at 8:16

edited Jun 25 '17 at 8:16

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

answered Jun 25 '17 at 8:03

chintan kotadiyachintan kotadiya

6231514

6231514

add a comment | 

add a comment | 

2

This is common since Laravel 5.4 changed the default database charater set to utf8mb4. What you have to do, is: edit your AppProviders.php by putting this code before the class declaration

use IlluminateSupportFacadesSchema;

Also, add this to the 'boot' function
Schema::defaultStringLength(191);

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

add a comment | 

2

This is common since Laravel 5.4 changed the default database charater set to utf8mb4. What you have to do, is: edit your AppProviders.php by putting this code before the class declaration

use IlluminateSupportFacadesSchema;

Also, add this to the 'boot' function
Schema::defaultStringLength(191);

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

add a comment | 

2

2

2

This is common since Laravel 5.4 changed the default database charater set to utf8mb4. What you have to do, is: edit your AppProviders.php by putting this code before the class declaration

use IlluminateSupportFacadesSchema;

Also, add this to the 'boot' function
Schema::defaultStringLength(191);

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

This is common since Laravel 5.4 changed the default database charater set to utf8mb4. What you have to do, is: edit your AppProviders.php by putting this code before the class declaration

use IlluminateSupportFacadesSchema;

Also, add this to the 'boot' function
Schema::defaultStringLength(191);

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

share|improve this answer

share|improve this answer

answered Feb 8 '18 at 10:44

TreasureTreasure

646

answered Feb 8 '18 at 10:44

TreasureTreasure

646

answered Feb 8 '18 at 10:44

TreasureTreasure

646

646

add a comment | 

add a comment | 

2

update & insert these lines in app/Providers/AppServiceProvider.php

use IlluminateSupportFacadesSchema;  //insert this line

public function boot()

{

    Schema::defaultStringLength(191); //insert this line also

}

set your database engine in config/database.php in 'mysql' array

'engine' => 'InnoDB',

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

add a comment | 

2

update & insert these lines in app/Providers/AppServiceProvider.php

use IlluminateSupportFacadesSchema;  //insert this line

public function boot()

{

    Schema::defaultStringLength(191); //insert this line also

}

set your database engine in config/database.php in 'mysql' array

'engine' => 'InnoDB',

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

add a comment | 

2

2

2

update & insert these lines in app/Providers/AppServiceProvider.php

use IlluminateSupportFacadesSchema;  //insert this line

public function boot()

{

    Schema::defaultStringLength(191); //insert this line also

}

set your database engine in config/database.php in 'mysql' array

'engine' => 'InnoDB',

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

update & insert these lines in app/Providers/AppServiceProvider.php

use IlluminateSupportFacadesSchema;  //insert this line

public function boot()

{

    Schema::defaultStringLength(191); //insert this line also

}

set your database engine in config/database.php in 'mysql' array

'engine' => 'InnoDB',

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

share|improve this answer

share|improve this answer

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

answered Sep 28 '18 at 18:15

Anjani BarnwalAnjani Barnwal

18526

18526

add a comment | 

add a comment | 

2

I have just modified following line in users and password_resets migration file.

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

New : $table->string('email', 128)->unique();

Voila!!

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

add a comment | 

2

I have just modified following line in users and password_resets migration file.

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

New : $table->string('email', 128)->unique();

Voila!!

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

add a comment | 

2

2

2

I have just modified following line in users and password_resets migration file.

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

New : $table->string('email', 128)->unique();

Voila!!

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

I have just modified following line in users and password_resets migration file.

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

New : $table->string('email', 128)->unique();

Voila!!

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

share|improve this answer

share|improve this answer

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

edited Jan 4 at 6:49

Dexter Bengil

2,35332236

2,35332236

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

answered Nov 16 '18 at 18:34

Mahesh GaikwadMahesh Gaikwad

263

263

add a comment | 

add a comment | 

2

If you face this error while work on laravel while using command: php artisan migrate
then you just add 2 lines in the file: app->Providers->AppServiceProvider.php

1. use Schema;


2. Schema::defaultStringLength(191);

please check this image.
then run php artisan migrate command again.

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

add a comment | 

2

If you face this error while work on laravel while using command: php artisan migrate
then you just add 2 lines in the file: app->Providers->AppServiceProvider.php

1. use Schema;


2. Schema::defaultStringLength(191);

please check this image.
then run php artisan migrate command again.

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

add a comment | 

2

2

2

If you face this error while work on laravel while using command: php artisan migrate
then you just add 2 lines in the file: app->Providers->AppServiceProvider.php

1. use Schema;


2. Schema::defaultStringLength(191);

please check this image.
then run php artisan migrate command again.

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

If you face this error while work on laravel while using command: php artisan migrate
then you just add 2 lines in the file: app->Providers->AppServiceProvider.php

1. use Schema;


2. Schema::defaultStringLength(191);

please check this image.
then run php artisan migrate command again.

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

share|improve this answer

share|improve this answer

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

edited Mar 7 at 9:17

Udhav Sarvaiya

2,34071930

2,34071930

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

answered Jan 17 at 4:52

Abdul RasheedAbdul Rasheed

212

212

add a comment | 

add a comment | 

1

In order to avoid changing anything in your code, simply update your MySQL server to at least 5.7.7

Reference this for more info : https://laravel-news.com/laravel-5-4-key-too-long-error

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

add a comment | 

1

In order to avoid changing anything in your code, simply update your MySQL server to at least 5.7.7

Reference this for more info : https://laravel-news.com/laravel-5-4-key-too-long-error

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

add a comment | 

1

1

1

In order to avoid changing anything in your code, simply update your MySQL server to at least 5.7.7

Reference this for more info : https://laravel-news.com/laravel-5-4-key-too-long-error

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

In order to avoid changing anything in your code, simply update your MySQL server to at least 5.7.7

Reference this for more info : https://laravel-news.com/laravel-5-4-key-too-long-error

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

share|improve this answer

share|improve this answer

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

answered Dec 6 '17 at 15:43

F.E Noel NfebeF.E Noel Nfebe

360218

360218

add a comment | 

add a comment | 

1

I think to force StringLenght to 191 is a really bad idea.
So I investigate to understand what is going on.

I noticed that this message error :

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key
was too long; max key length is 767 bytes

Started to show up after I updated my MySQL version. So I've checked the tables with PHPMyAdmin and I've noticed that all the new tables created were with the collation utf8mb4_unicode_ci instead of utf8_unicode_ci for the old ones.

In my doctrine config file, I noticed that charset was set to utf8mb4, but all my previous tables were created in utf8, so I guess this is some update magic that it start to work on utf8mb4.

Now the easy fix is to change the line charset in your ORM config file.
Then to drop the tables using utf8mb4_unicode_ci if you are in dev mode or fixe the charset if you can't drop them.

For Symfony 4

change charset: utf8mb4 to charset: utf8 in config/packages/doctrine.yaml

Now my doctrine migrations are working again just fine.

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks it's work for my ubuntu !
  
  – Crown Backend
  Jan 7 at 19:38
  

  
  
  
  

add a comment | 

1

I think to force StringLenght to 191 is a really bad idea.
So I investigate to understand what is going on.

I noticed that this message error :

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key
was too long; max key length is 767 bytes

Started to show up after I updated my MySQL version. So I've checked the tables with PHPMyAdmin and I've noticed that all the new tables created were with the collation utf8mb4_unicode_ci instead of utf8_unicode_ci for the old ones.

In my doctrine config file, I noticed that charset was set to utf8mb4, but all my previous tables were created in utf8, so I guess this is some update magic that it start to work on utf8mb4.

Now the easy fix is to change the line charset in your ORM config file.
Then to drop the tables using utf8mb4_unicode_ci if you are in dev mode or fixe the charset if you can't drop them.

For Symfony 4

change charset: utf8mb4 to charset: utf8 in config/packages/doctrine.yaml

Now my doctrine migrations are working again just fine.

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks it's work for my ubuntu !
  
  – Crown Backend
  Jan 7 at 19:38
  

  
  
  
  

add a comment | 

1

1

1

I think to force StringLenght to 191 is a really bad idea.
So I investigate to understand what is going on.

I noticed that this message error :

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key
was too long; max key length is 767 bytes

Started to show up after I updated my MySQL version. So I've checked the tables with PHPMyAdmin and I've noticed that all the new tables created were with the collation utf8mb4_unicode_ci instead of utf8_unicode_ci for the old ones.

In my doctrine config file, I noticed that charset was set to utf8mb4, but all my previous tables were created in utf8, so I guess this is some update magic that it start to work on utf8mb4.

Now the easy fix is to change the line charset in your ORM config file.
Then to drop the tables using utf8mb4_unicode_ci if you are in dev mode or fixe the charset if you can't drop them.

For Symfony 4

change charset: utf8mb4 to charset: utf8 in config/packages/doctrine.yaml

Now my doctrine migrations are working again just fine.

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

I think to force StringLenght to 191 is a really bad idea.
So I investigate to understand what is going on.

I noticed that this message error :

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key
was too long; max key length is 767 bytes

Started to show up after I updated my MySQL version. So I've checked the tables with PHPMyAdmin and I've noticed that all the new tables created were with the collation utf8mb4_unicode_ci instead of utf8_unicode_ci for the old ones.

In my doctrine config file, I noticed that charset was set to utf8mb4, but all my previous tables were created in utf8, so I guess this is some update magic that it start to work on utf8mb4.

Now the easy fix is to change the line charset in your ORM config file.
Then to drop the tables using utf8mb4_unicode_ci if you are in dev mode or fixe the charset if you can't drop them.

For Symfony 4

change charset: utf8mb4 to charset: utf8 in config/packages/doctrine.yaml

Now my doctrine migrations are working again just fine.

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

share|improve this answer

share|improve this answer

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

answered May 17 '18 at 9:03

Kaizoku GambareKaizoku Gambare

1,1621125

1,1621125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks it's work for my ubuntu !
  
  – Crown Backend
  Jan 7 at 19:38
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks it's work for my ubuntu !
  
  – Crown Backend
  Jan 7 at 19:38
  

  
  
  
  

Thanks it's work for my ubuntu !

– Crown Backend
Jan 7 at 19:38

Thanks it's work for my ubuntu !

– Crown Backend
Jan 7 at 19:38

add a comment | 

1

The recommended solution is to enable innodb_large_prefix option of MySQL so you won't be getting into subsequent problems. And here is how to do that:

Open the my.ini MySQL configuration file and add the below lines under the [mysqld] line like this.

[mysqld]

innodb_file_format = Barracuda

innodb_large_prefix = 1

innodb_file_per_table = ON

After that, save your changes and restart your MySQL service.

Rollback if you need to and then re-run your migration.

---

Just in case your problem still persists, go to your database configuration file and set

'engine' => null, to 'engine' => 'innodb row_format=dynamic'

Hope it helps!

share|improve this answer

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

add a comment | 

1

The recommended solution is to enable innodb_large_prefix option of MySQL so you won't be getting into subsequent problems. And here is how to do that:

Open the my.ini MySQL configuration file and add the below lines under the [mysqld] line like this.

[mysqld]

innodb_file_format = Barracuda

innodb_large_prefix = 1

innodb_file_per_table = ON

After that, save your changes and restart your MySQL service.

Rollback if you need to and then re-run your migration.

---

Just in case your problem still persists, go to your database configuration file and set

'engine' => null, to 'engine' => 'innodb row_format=dynamic'

Hope it helps!

share|improve this answer

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

add a comment | 

1

1

1

The recommended solution is to enable innodb_large_prefix option of MySQL so you won't be getting into subsequent problems. And here is how to do that:

Open the my.ini MySQL configuration file and add the below lines under the [mysqld] line like this.

[mysqld]

innodb_file_format = Barracuda

innodb_large_prefix = 1

innodb_file_per_table = ON

After that, save your changes and restart your MySQL service.

Rollback if you need to and then re-run your migration.

---

Just in case your problem still persists, go to your database configuration file and set

'engine' => null, to 'engine' => 'innodb row_format=dynamic'

Hope it helps!

share|improve this answer

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

The recommended solution is to enable innodb_large_prefix option of MySQL so you won't be getting into subsequent problems. And here is how to do that:

Open the my.ini MySQL configuration file and add the below lines under the [mysqld] line like this.

[mysqld]

innodb_file_format = Barracuda

innodb_large_prefix = 1

innodb_file_per_table = ON

After that, save your changes and restart your MySQL service.

Rollback if you need to and then re-run your migration.

---

Just in case your problem still persists, go to your database configuration file and set

'engine' => null, to 'engine' => 'innodb row_format=dynamic'

Hope it helps!

share|improve this answer

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

share|improve this answer

share|improve this answer

edited Nov 30 '18 at 7:28

edited Nov 30 '18 at 7:28

edited Nov 30 '18 at 7:28

answered Nov 28 '18 at 7:59

SammieSammie

322711

answered Nov 28 '18 at 7:59

SammieSammie

322711

answered Nov 28 '18 at 7:59

SammieSammie

322711

322711

add a comment | 

add a comment | 

1

1- Go to /config/database.php and find these lines

'mysql' => [

    ...,

    'charset' => 'utf8mb4',

    'collation' => 'utf8mb4_unicode_ci',

    ...,

    'engine' => null,

 ]

and change them to:

'mysql' => [

    ...,

    'charset' => 'utf8',

    'collation' => 'utf8_unicode_ci',

    ...,

    'engine' => 'InnoDB',

 ]

2- Run php artisan config:cache to reconfigure laravel

3- Delete the existing tables in your database and then run php artisan migrate again

share|improve this answer

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

add a comment | 

1

1- Go to /config/database.php and find these lines

'mysql' => [

    ...,

    'charset' => 'utf8mb4',

    'collation' => 'utf8mb4_unicode_ci',

    ...,

    'engine' => null,

 ]

and change them to:

'mysql' => [

    ...,

    'charset' => 'utf8',

    'collation' => 'utf8_unicode_ci',

    ...,

    'engine' => 'InnoDB',

 ]

2- Run php artisan config:cache to reconfigure laravel

3- Delete the existing tables in your database and then run php artisan migrate again

share|improve this answer

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

add a comment | 

1

1

1

1- Go to /config/database.php and find these lines

'mysql' => [

    ...,

    'charset' => 'utf8mb4',

    'collation' => 'utf8mb4_unicode_ci',

    ...,

    'engine' => null,

 ]

and change them to:

'mysql' => [

    ...,

    'charset' => 'utf8',

    'collation' => 'utf8_unicode_ci',

    ...,

    'engine' => 'InnoDB',

 ]

2- Run php artisan config:cache to reconfigure laravel

3- Delete the existing tables in your database and then run php artisan migrate again

share|improve this answer

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

1- Go to /config/database.php and find these lines

'mysql' => [

    ...,

    'charset' => 'utf8mb4',

    'collation' => 'utf8mb4_unicode_ci',

    ...,

    'engine' => null,

 ]

and change them to:

'mysql' => [

    ...,

    'charset' => 'utf8',

    'collation' => 'utf8_unicode_ci',

    ...,

    'engine' => 'InnoDB',

 ]

2- Run php artisan config:cache to reconfigure laravel

3- Delete the existing tables in your database and then run php artisan migrate again

share|improve this answer

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

share|improve this answer

share|improve this answer

edited Feb 15 at 17:41

edited Feb 15 at 17:41

edited Feb 15 at 17:41

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

answered Feb 8 at 8:10

mohammad asgharimohammad asghari

16819

16819

add a comment | 

add a comment | 

0

For anyone else who might run into this, my issue was that I was making a column of type string and trying to make it ->unsigned() when I meant for it to be an integer.

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

add a comment | 

0

For anyone else who might run into this, my issue was that I was making a column of type string and trying to make it ->unsigned() when I meant for it to be an integer.

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

add a comment | 

0

0

0

For anyone else who might run into this, my issue was that I was making a column of type string and trying to make it ->unsigned() when I meant for it to be an integer.

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

For anyone else who might run into this, my issue was that I was making a column of type string and trying to make it ->unsigned() when I meant for it to be an integer.

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

share|improve this answer

share|improve this answer

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

answered Apr 25 '18 at 19:20

Brynn BatemanBrynn Bateman

435516

435516

add a comment | 

add a comment | 

0

The approached that work here was pass a second param with the key name (a short one):

$table->string('my_field_name')->unique(null,'key_name');

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

add a comment | 

0

The approached that work here was pass a second param with the key name (a short one):

$table->string('my_field_name')->unique(null,'key_name');

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

add a comment | 

0

0

0

The approached that work here was pass a second param with the key name (a short one):

$table->string('my_field_name')->unique(null,'key_name');

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

The approached that work here was pass a second param with the key name (a short one):

$table->string('my_field_name')->unique(null,'key_name');

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

share|improve this answer

share|improve this answer

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

answered Jul 24 '18 at 13:23

Tiago GouvêaTiago Gouvêa

5,17413445

5,17413445

add a comment | 

add a comment | 

0

In AppServiceProvider.php file:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

add a comment | 

0

In AppServiceProvider.php file:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

add a comment | 

0

0

0

In AppServiceProvider.php file:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

In AppServiceProvider.php file:

use IlluminateSupportFacadesSchema;



public function boot()

{

    Schema::defaultStringLength(191);

}

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

share|improve this answer

share|improve this answer

edited Mar 7 at 5:10

Inzamam Idrees

784318

edited Mar 7 at 5:10

Inzamam Idrees

784318

edited Mar 7 at 5:10

Inzamam Idrees

784318

784318

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

answered Mar 7 at 4:40

Uddyan SemwalUddyan Semwal

4011

4011

add a comment | 

add a comment | 

-1

For me what worked was to update the dependencies by running.

composer update

You should also install the latest mysql version.

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

add a comment | 

-1

For me what worked was to update the dependencies by running.

composer update

You should also install the latest mysql version.

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

add a comment | 

-1

-1

-1

For me what worked was to update the dependencies by running.

composer update

You should also install the latest mysql version.

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

For me what worked was to update the dependencies by running.

composer update

You should also install the latest mysql version.

composer update

composer update

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

share|improve this answer

share|improve this answer

answered Aug 28 '18 at 14:09

MateoMateo

536

answered Aug 28 '18 at 14:09

MateoMateo

536

answered Aug 28 '18 at 14:09

MateoMateo

536

536

add a comment | 

add a comment | 

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f42244541%2flaravel-migration-error-syntax-error-or-access-violation-1071-specified-key-wa%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

This page is only for reference, If you need detailed information, please check here