These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | use Illuminate\Database\Schema\Blueprint; |
||
4 | use Illuminate\Database\Migrations\Migration; |
||
5 | |||
6 | class CreateUsersActivationTable extends Migration |
||
0 ignored issues
–
show
|
|||
7 | { |
||
8 | /** |
||
9 | * Run the migrations. |
||
10 | * |
||
11 | * @return void |
||
12 | */ |
||
13 | public function up() |
||
14 | { |
||
15 | Schema::create('users_activations', function (Blueprint $table) { |
||
16 | $table->engine = 'InnoDB'; |
||
17 | $table->increments('id'); |
||
18 | $table->unsignedInteger('user_id'); |
||
19 | $table->string('code'); |
||
20 | $table->boolean('completed')->default(0); |
||
21 | $table->timestamp('completed_at')->nullable(); |
||
22 | $table->timestamps(); |
||
23 | |||
24 | $table->foreign('user_id')->references('id')->on('users')->onUpdate('cascade')->onDelete('cascade'); |
||
25 | }); |
||
26 | } |
||
27 | |||
28 | /** |
||
29 | * Reverse the migrations. |
||
30 | * |
||
31 | * @return void |
||
32 | */ |
||
33 | public function down() |
||
34 | { |
||
35 | Schema::drop('users_activations'); |
||
36 | } |
||
37 | } |
||
38 |
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.