Fixed DB seeder to truncate the asset_maintenances table

This wouldn’t have affected anything in production, but could cause some weird behavior if re-seeding often, since the suppliers table gets stomped on but the old maintenances remained, leaving ghost entries and associating the wrong (old, now defunct) supplier with the maintenance as new supplier IDs get generated.
This commit is contained in:
snipe 2020-09-04 16:23:58 -07:00
parent 10648de9af
commit acd15bc3e4
No known key found for this signature in database
GPG key ID: 10BFFDA3ED34B5AC

View file

@ -48,6 +48,7 @@ class DatabaseSeeder extends Seeder
Model::reguard();
DB::table('imports')->truncate();
DB::table('asset_maintenances')->truncate();
}
}