1. I noticed some changes in the database migration files in the Git repository, such as the field mine_type being changed to mime_type. See Figure 1.
2. These two database migration files happened to be in the last migration batch. See Figure 2.
3. To roll back the last migration operation, you can use the Artisan command rollback. This command rolls back the last “batch” of migrations, which may include multiple migration files, but it prompts: Migration not found. See Figure 3.
PS E:\wwwroot\object> php artisan migrate:rollback
Migration not found: 2021_12_13_145303_create_theme_asset_version_table
Migration not found: 2021_12_06_133918_create_theme_asset_table
PS E:\wwwroot\object>
4. The reason should be that these two migration files are located inside a module, at the path: /Modules/ThemeStore/Database/Migrations, and do not exist in the default path: /database/migrations.
5. The module implementation is based on nwidart/laravel-modules, so I executed the module:migrate-rollback command. The execution was successful. See Figure 4.
PS E:\wwwroot\object> php artisan module:migrate-rollback ThemeStore
Rollback: 2021_12_13_145303_create_theme_asset_version_table
Rollback: 2021_12_06_133918_create_theme_asset_table
PS E:\wwwroot\object> php artisan module:migrate ThemeStore
Migrating: 2021_12_06_133918_create_theme_asset_table
Migrated: 2021_12_06_133918_create_theme_asset_table (0.26 seconds)
Migrating: 2021_12_13_145303_create_theme_asset_version_table
Migrated: 2021_12_13_145303_create_theme_asset_version_table (0.02 seconds)
PS E:\wwwroot\object>
6. I checked the database table, and the field name has been changed to: mime_type. See Figure 5.
