Completed
Push — dev ( 9049a0 )
by Amr
05:18
created

AddOwnerIdToSettingsTable::up()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 6
Code Lines 3

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
c 0
b 0
f 0
dl 0
loc 6
rs 9.4285
cc 1
eloc 3
nc 1
nop 0
1
<?php
2
3
use Illuminate\Support\Facades\Schema;
4
use Illuminate\Database\Schema\Blueprint;
5
use Illuminate\Database\Migrations\Migration;
6
7
class AddOwnerIdToSettingsTable extends Migration
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
8
{
9
    /**
10
     * Run the migrations.
11
     *
12
     * @return void
13
     */
14
    public function up()
15
    {
16
        Schema::table('settings', function (Blueprint $table) {
17
            $table->unsignedInteger('owner_id')->nullable();
18
        });
19
    }
20
21
    /**
22
     * Reverse the migrations.
23
     *
24
     * @return void
25
     */
26
    public function down()
27
    {
28
        Schema::table('settings', function (Blueprint $table) {
29
            $table->dropColumn('owner_id');
30
        });
31
    }
32
}
33