Refactoring item_user migration

Delete the separate value for item_user,
adding a primary key to the pivot table
and removing the timestamp as it is
not necessary.

database/migrations/2018_09_08_192152_create_items_table.php

@@ -21,6 +21,13 @@ class CreateItemsTable extends Migration
             $table->integer('waiting_user_id')->nullable();
             $table->timestamps();
         });
+
+        Schema::create('item_user', function (Blueprint $table) {
+            $table->increments('id');
+            $table->integer('item_id');
+            $table->integer('user_id');
+            $table->primary(['item_id', 'user_id']);
+        });
     }
 
     /**
@@ -31,5 +38,6 @@ class CreateItemsTable extends Migration
     public function down()
     {
         Schema::dropIfExists('items');
+        Schema::dropIfExists('item_user');
     }
 }

database/migrations/2018_09_10_233609_item_user.php

@@ -1,33 +0,0 @@
-<?php
-
-use Illuminate\Support\Facades\Schema;
-use Illuminate\Database\Schema\Blueprint;
-use Illuminate\Database\Migrations\Migration;
-
-class ItemUser extends Migration
-{
-    /**
-     * Run the migrations.
-     *
-     * @return void
-     */
-    public function up()
-    {
-        Schema::create('item_user', function (Blueprint $table) {
-            $table->increments('id');
-            $table->integer('item_id');
-            $table->integer('user_id');
-            $table->timestamps();
-        });
-    }
-
-    /**
-     * Reverse the migrations.
-     *
-     * @return void
-     */
-    public function down()
-    {
-        Schema::dropIfExists('item_user');
-    }
-}