Completed
Push — master ( 857394...4794c5 )
by Mahmoud
03:25
created

CreatePaypalAccountsTable::down()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 4
rs 10
c 0
b 0
f 0
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
3
use Illuminate\Database\Migrations\Migration;
4
use Illuminate\Database\Schema\Blueprint;
5
6
/**
7
 * Class CreatePaypalAccountsTable
8
 *
9
 * @author  Mahmoud Zalt  <[email protected]>
10
 */
11
class CreatePaypalAccountsTable 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...
12
{
13
14
    /**
15
     * Run the migrations.
16
     *
17
     * @return void
18
     */
19
    public function up()
20
    {
21
        Schema::create('paypal_accounts', function (Blueprint $table) {
22
            $table->increments('id');
23
24
            $table->string('some_id');
25
26
            $table->integer('user_id')->unsigned();
27
            $table->foreign('user_id')->references('id')->on('users');
28
29
            $table->timestamps();
30
            $table->softDeletes();
31
        });
32
    }
33
34
    /**
35
     * Reverse the migrations.
36
     *
37
     * @return void
38
     */
39
    public function down()
40
    {
41
        Schema::drop('paypal_accounts');
42
    }
43
}
44