1 | <?php |
||
2 | |||
3 | use Illuminate\Support\Facades\Schema; |
||
4 | use Illuminate\Database\Schema\Blueprint; |
||
5 | use Illuminate\Database\Migrations\Migration; |
||
6 | |||
7 | class DeviceGroupsRewrite extends Migration |
||
0 ignored issues
–
show
|
|||
8 | { |
||
9 | /** |
||
10 | * Run the migrations. |
||
11 | * |
||
12 | * @return void |
||
13 | */ |
||
14 | public function up() |
||
15 | { |
||
16 | Schema::table('device_groups', function (Blueprint $table) { |
||
17 | $table->string('desc')->nullable()->change(); |
||
18 | $table->string('type', 16)->default('dynamic')->after('desc'); |
||
19 | $table->text('rules')->nullable()->after('type'); |
||
20 | $table->dropColumn('params'); |
||
21 | }); |
||
22 | } |
||
23 | |||
24 | /** |
||
25 | * Reverse the migrations. |
||
26 | * |
||
27 | * @return void |
||
28 | */ |
||
29 | public function down() |
||
30 | { |
||
31 | Schema::table('device_groups', function (Blueprint $table) { |
||
32 | $table->string('desc')->change(); |
||
33 | $table->dropColumn('type'); |
||
34 | $table->dropColumn('rules'); |
||
35 | $table->text('params')->nullable()->after('pattern'); |
||
36 | }); |
||
37 | } |
||
38 | } |
||
39 |
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.