1005 Can't create table `db`.`reports` (errno: 150 "Foreign key constraint is incorrectly formed

Thanks a lot for your help @webard , i will refactor all my code and implement the newer way what Tray2 suggested and see

@Tray2 Many thanks for your help, also for catching longText, i though i needed it for store title in 3 different languages, but i would stay with text since this should be enough.

The way you suggested is more organised and having less code as well. I see that we don't have to mention anymore the id ( category_report_id) which is needed to be called in my Report model like

 public function category()
     {
         return $this->belongsTo(CategoryReport::class,'category_report_id');
     }

My question is which id i can call on this method ?

@Zoul You don't have to pass any second parameter, it is only necessary if you cal the foreign key something else than category_report_id which you don't when you use the

 $table->foreignIdFor(CategoryReports::class)
				->constrained()
				->onDelete('cascade');

@Tray2 thank you so much for your support. I did refactor my code and i guess it passed for the above tables, however i have another :

 Cannot declare class App\Models\CreateGalleriesPhotosTable, because the name is already in use

  at database\migrations21_06_11_090235_create_galleries__photos_table.php:7
      3▕ use Illuminate\Database\Migrations\Migration;
      4▕ use Illuminate\Database\Schema\Blueprint;
      5▕ use Illuminate\Support\Facades\Schema;
      6▕
  ➜   7▕ class CreateGalleriesPhotosTable extends Migration
      8▕ {
      9▕     /**
     10▕      * Run the migrations.
     11▕      *


   Whoops\Exception\ErrorException 

  Cannot declare class App\Models\CreateGalleriesPhotosTable, because the name is already in use

  at database\migrations21_06_11_090235_create_galleries__photos_table.php:7
      3▕ use Illuminate\Database\Migrations\Migration;
      4▕ use Illuminate\Database\Schema\Blueprint;
      5▕ use Illuminate\Support\Facades\Schema;
      6▕
  ➜   7▕ class CreateGalleriesPhotosTable extends Migration
      8▕ {
      9▕     /**
     10▕      * Run the migrations.
     11▕      *

  1   vendor\filp\whoops\src\Whoops\Run.php:510
      Whoops\Run::handleError("Cannot declare class App\Models\CreateGalleriesPhotosTable, because the name is already in use", "D:\xampp\htdocs\db\code\oaahdv1\database\migrations21_06_11_090235_create_galleries__photos_table.php")

  2   [internal]:0
      Whoops\Run::handleShutdown()

I cleared cached and tried to remove this table CreateGalleriesPhotosTable completely but i have again another error with other table

in CreateGalleriesPhotosTable table

class CreateGalleriesPhotosTable extends Migration  
{
    /**
     * Run the migrations.
     *
     * @return void 
     */
    public function up()
    {
        Schema::create('galleries_photos', function (Blueprint $table) {
            $table->id();
            $table->foreignIdFor(Gallery::class)->constrained()->onDelete('cascade');
            $table->string('photo')->nullable();
            $table->boolean('status')->default(false);
            $table->timestamps();
        });
    }

in galleries table

class CreateGalleriesTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('galleries', function (Blueprint $table) {
            $table->id();
            $table->text('title')->nullable();
            $table->text('description')->nullable();
            $table->timestamps();
        });
    }

Any idea what is going wrong pls ?

@Zoul it seems that you have a model with the same name as your migration class, or you managed to copy it to you models namespace.

@Tray2 thats could be the reason, but as i don't see any dublicate or mistmatch names its so hard to debug, will check deeper i might see the error