usually it means that when migrations happened, it didnt create the table as there was an error so the alter statement is failing

there could also be the case that one of the migrations might have a different table for down() section so when you rollback you accidentally delete the other table so when down() method for the actual table happens it gives an error (i have done this especially when i copy/paste a migration to create new ones)

now you can confirm this by logging in to SQL and checking whether that table exists or not..

if it does.. try running that SQL (alter statement) manually

shez1983 said:

usually it means that when migrations happened, it didnt create the table as there was an error so the alter statement is failing

there could also be the case that one of the migrations might have a different table for down() section so when you rollback you accidentally delete the other table so when down() method for the actual table happens it gives an error (i have done this especially when i copy/paste a migration to create new ones)

now you can confirm this by logging in to SQL and checking whether that table exists or not..

if it does.. try running that SQL (alter statement) manually

Sorry but I do not get it Im not good with SQL and Databases, I did made a new DB but that didn'tm work. What can I try to solve this?

astroanu said:

Schema::table is to modify an existing table, use Schema::create to create new. ;)

Dayum thats right, missed it completly!

astroanu. Thanks :-)

astroanu said:

Schema::table is to modify an existing table, use Schema::create to create new. ;) ....

woou its work thanks alot

Schema::table is to modify an existing table, use Schema::create to create new. ;)