skip to Main Content

Laravel bug: making column nullable stops it from being added to table

I have a SQLite database with the following migration defined: Schema::create("views", function(Blueprint $table){ $table->integer("match_id"); $table->string("pov"); $table->string("teams"); $table->text("moves"); $table->bigIncrements("id"); $table->date("created_at"); $table->date("updated_at"); }); Note: id is the primary key of the table, match_id should just be treated as any other column. This…

VIEW QUESTION
Back To Top
Search