php - Should I create table drop migration for unused tables? -

a simple question not find answer on google.

i have laravel 5.2 based project tables no longer needed: correct way create migration dropifexists in or should manually drop , delete migration responsible creation of table?

on 1 hand, migration gives me rollback option, can recreate table, on other hand, still stupid create table , drop again later. , migration ( if needed ) can found in repository.

you can drop or delete yor migration file tables not in use, define php artisan make:model test --migration when there need create migration file. or else if there need afterwards create migration file same php artisan make:migration.