![Laravel BigIncrements. Some weeks ago I had a migration that… | by Ariel Mejia Dev | Ariel Mejia Dev | Medium Laravel BigIncrements. Some weeks ago I had a migration that… | by Ariel Mejia Dev | Ariel Mejia Dev | Medium](https://cdn-images-1.medium.com/fit/t/1600/480/1*1RERMPCW2-x0N1a2nLsi-Q.jpeg)
Laravel BigIncrements. Some weeks ago I had a migration that… | by Ariel Mejia Dev | Ariel Mejia Dev | Medium
![Laravel Daily on Twitter: "#Laravel tip of the day: Laravel 5.8 default users migration changed "id" field from increments() to bigIncrements(). Which means every foreign key to users table should also be Laravel Daily on Twitter: "#Laravel tip of the day: Laravel 5.8 default users migration changed "id" field from increments() to bigIncrements(). Which means every foreign key to users table should also be](https://pbs.twimg.com/media/D1YEc3EX0AAcRJx.jpg)
Laravel Daily on Twitter: "#Laravel tip of the day: Laravel 5.8 default users migration changed "id" field from increments() to bigIncrements(). Which means every foreign key to users table should also be
![php - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'payments' already exists (SQL: create table `payments` - Stack Overflow php - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'payments' already exists (SQL: create table `payments` - Stack Overflow](https://i.stack.imgur.com/OrZvl.png)