Level 2
I think because not all developers use soft deleted
however it will be a new feature in 5.8
1 like
Feb 14, 2019
5
Level 1
Why isn't the 'deleted_at' datetime field auto-casted?
I see (from tinkering with Nova) that the 'deleted_at' datetime field (as generated by $table->softDeletes(); in a migration) is not auto-casted to a DateTime or Carbon instance.
BUT the $table->timestamps(); datetime fields are indeed auto-casted by Laravel: "By default, Eloquent will convert the created_at and updated_at columns to instances of Carbon, which extends the PHP DateTime class".
So I am simply curious to hear if there is any special practical or technical reason to exclude 'deleted_at' from auto-casting?
Many thanks, Dev Master
Level 1
@ARTHVRIAN - Thanks for the news, it does indeed look like 5.8 will change some of the Carbon integrations.
Level 67
Because it's optional. You just have to add the trait to the model(s) and $dates array that use it like the docs show:
To enable soft deletes for a model, use the
Illuminate\Database\Eloquent\SoftDeletestrait on the model and add the deleted_at column to your $dates property:
1 like
Level 1
Level 1
Yep, does indeed look like auto casting of the soft delete timestamp was added in for 5.8 https://laravel.com/docs/master/upgrade#model-names-ending-with-irregular-plurals (and then scroll down a bit)
Please or to participate in this conversation.