for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
class CreateVacanciesTable extends Migration
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.
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
Schema::create('vacancies', function (Blueprint $table) {
$table->increments('id');
$table->date('date');
$table->timestamp('start_at')->nullable()->index();
$table->timestamp('finish_at')->nullable()->index();
$table->integer('business_id')->unsigned();
$table->foreign('business_id')->references('id')->on('businesses');
$table->integer('service_id')->unsigned();
$table->foreign('service_id')->references('id')->on('services')->onDelete('cascade');
$table->integer('humanresource_id')->unsigned()->nullable();
$table->foreign('humanresource_id')->references('id')->on('humanresources')->onDelete('cascade');
$table->integer('capacity')->unsigned()->default(1);
$table->nullableTimestamps();
});
}
* Reverse the migrations.
public function down()
Schema::drop('vacancies');
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.