Hi. I'm migrating an old database to a Laravel-based app. One issue I'm coming across is that during the migration (a DB seeder), when deleted_at (and, in fact, all timestamp fields) does not have a value, it is being set at 0000-00-00 00:00:00. This breaks a lot of the functionality because those values are not null and their records are being treated as trashed incorrectly. Any idea on where to start tracking down the problem?
I should add that on the Model, $softDelete is set to true and the schema is using $table->softDeletes(). The DB Seeder is not setting deleted_at at all (unless it is actually deleted).
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community