search

ttungbmt / filament-ban

Laravel Filament Ban simplify blocking and banning Eloquent models.
MIT License
11 stars 3 forks source link

Double migration #5

Open Simoneu01 opened 2 years ago

Simoneu01 commented 2 years ago

Please remove your extra stub of the create bans table, is useless since the package cybercog/laravel-ban has already the migration

php artisan migrate

   INFO  Running migrations.

  2017_03_04_000000_create_bans_table ................................................................................................... 198ms DONE
  2022_08_29_130102_create_bans_table ..................................................................................................... 2ms FAIL
mcfaith9 commented 1 year ago

Yep I also encounter this, double migration

   INFO  Running migrations.

  2017_03_04_000000_create_bans_table ..................................................................... 121ms DONE
  2023_04_19_073338_create_bans_table ....................................................................... 2ms FAIL

   Illuminate\Database\QueryException 

   SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'bans' already exists (SQL: create table `bans` (`id` int unsigned not null auto_increment primary key, `bannable_type` varchar(255) not null, `bannable_id` bigint unsigned not null, `created_by_type` varchar(255) null, `created_by_id` bigint unsigned null, `comment` text null, `expired_at` timestamp null, `deleted_at` timestamp null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')

I see your comment already a year ahead

jayomayan commented 1 year ago

seems like this is not maintained anymore