CreateSktmsTable::up()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 13
Code Lines 10

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 10
nc 1
nop 0
dl 0
loc 13
rs 9.4285
c 0
b 0
f 0
1
<?php
2
3
use Illuminate\Database\Migrations\Migration;
4
use Illuminate\Database\Schema\Blueprint;
5
6
class CreateSktmsTable 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...
7
{
8
    /**
9
     * Run the migrations.
10
     *
11
     * @return void
12
     */
13
	public function up()
14
	{
15
		Schema::create('sktms', function(Blueprint $table) {
16
			$table->increments('id');
17
			$table->string('nomor_un');
18
			$table->integer('master_sktm_id')->nullable();
19
			$table->string('no_sktm');
20
			$table->integer('nilai')->nullable();
21
			$table->integer('user_id')->nullable();
22
			$table->timestamps();
23
			$table->softDeletes();
24
		});
25
	}
26
27
    /**
28
     * Reverse the migrations.
29
     *
30
     * @return void
31
     */
32
	public function down()
33
	{
34
		Schema::drop('sktms');
35
	}
36
}
37