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 CreateBusinessContactPivotTable 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('business_contact', function (Blueprint $table) {
$table->integer('business_id')->unsigned()->index();
$table->foreign('business_id')->references('id')->on('businesses')->onDelete('cascade');
$table->integer('contact_id')->unsigned()->index();
$table->foreign('contact_id')->references('id')->on('contacts')->onDelete('cascade');
$table->string('notes')->nullable();
$table->nullableTimestamps();
$table->unique(['business_id', 'contact_id']);
});
}
* Reverse the migrations.
public function down()
Schema::drop('business_contact');
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.