Soft deletion in Laravel Eloquent marks records as deleted rather than actually removed by adding the deleted_at column. 1. Use the SoftDeletes feature and introduce it in the model; 2. The database table needs to contain the deleted_at column, which is usually added by the migration file using $table->softDeletes(); 3. Only the deleted_at timestamp is set when calling the delete() method; 4. The default query does not contain soft delete records, but can be obtained through withTrashed() or onlyTrashed(); 5. Use forceDelete() to completely delete soft delete records; 6. Restore soft delete records through the restore() method, supporting batch recovery. This mechanism allows data recovery without affecting normal query results.
Soft deletes in Laravel Eloquent are a way to "delete" records from the database without actually removing them. Instead of permanently deleting a row, Laravel marks it as deleted by setting a deleted_at
timestamp column. This allows you to restore the record later or filter it out from regular queries.

How Soft Deletes Work
When you enable soft deletes on a model, Laravel automatically modifies all query operations to exclude any records where deleted_at
is not null. This means that unless you explicitly ask for soft-deleted records, they won't show up in your results.
To use soft deletes:

- Add the
SoftDeletes
trait to your model. - Make sure your database table has a
deleted_at
column (usually created using$table->softDeletes();
in migrations).
Once set up, calling delete()
on a model instance won't remove it from the database — it will just set the deleted_at
field to the current timestamp.
Enabling Soft Deletes in a Model
To enable soft deletes for a model, follow these steps:

-
Import and use the
SoftDeletes
trait:use Illuminate\Database\Eloquent\SoftDeletes;
Add the trait inside your model:
class User extends Model { use SoftDeletes; }
Update the corresponding migration file to include the
deleted_at
column:$table->softDeletes();
This setup ensures that when you delete a record, it's only marked as deleted, not removed.
Note: If you're modifying an existing table, make sure to create a new migration to add the
deleted_at
column.
Querying Soft Deleted Records
By default, Eloquent hides soft-deleted records. But sometimes, you may want to retrieve them:
Use
withTrashed()
to include soft-deleted records in your query:User::withTrashed()->find(1);
Use
onlyTrashed()
to get only the soft-deleted ones:User::onlyTrashed()->get();
These methods are useful when you need to display or restore previously deleted data.
If you want to completely remove a soft-deleted record from the database, use forceDelete()
:
$user = User::onlyTrashed()->find(1); $user->forceDelete();
Restoring Soft Deleted Records
You can bring back a soft-deleted record by calling the restore()
method:
$user = User::onlyTrashed()->find(1); $user->restore();
This clears the deleted_at
value and makes the record visible again in normal queries.
Restoring multiple records at once? No problem:
User::onlyTrashed()->where('created_at', '<', '2024-01-01')->restore();
Just remember, restoring doesn't affect relationships by default. You'll have to handle those manually if needed.
Basically that's it.
The above is the detailed content of How does Soft Deletes work in Laravel Eloquent?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

InLaravel,policiesorganizeauthorizationlogicformodelactions.1.Policiesareclasseswithmethodslikeview,create,update,anddeletethatreturntrueorfalsebasedonuserpermissions.2.Toregisterapolicy,mapthemodeltoitspolicyinthe$policiesarrayofAuthServiceProvider.

Yes,youcaninstallLaravelonanyoperatingsystembyfollowingthesesteps:1.InstallPHPandrequiredextensionslikembstring,openssl,andxmlusingtoolslikeXAMPPonWindows,HomebrewonmacOS,oraptonLinux;2.InstallComposer,usinganinstalleronWindowsorterminalcommandsonmac

The main role of the controller in Laravel is to process HTTP requests and return responses to keep the code neat and maintainable. By concentrating the relevant request logic into a class, the controller makes the routing file simpler, such as putting user profile display, editing and deletion operations in different methods of UserController. The creation of a controller can be implemented through the Artisan command phpartisanmake:controllerUserController, while the resource controller is generated using the --resource option, covering methods for standard CRUD operations. Then you need to bind the controller in the route, such as Route::get('/user/{id

Laravel allows custom authentication views and logic by overriding the default stub and controller. 1. To customize the authentication view, use the command phpartisanvendor:publish-tag=laravel-auth to copy the default Blade template to the resources/views/auth directory and modify it, such as adding the "Terms of Service" check box. 2. To modify the authentication logic, you need to adjust the methods in RegisterController, LoginController and ResetPasswordController, such as updating the validator() method to verify the added field, or rewriting r

Laravelprovidesrobusttoolsforvalidatingformdata.1.Basicvalidationcanbedoneusingthevalidate()methodincontrollers,ensuringfieldsmeetcriterialikerequired,maxlength,oruniquevalues.2.Forcomplexscenarios,formrequestsencapsulatevalidationlogicintodedicatedc

InLaravelBladetemplates,use{{{...}}}todisplayrawHTML.Bladeescapescontentwithin{{...}}usinghtmlspecialchars()topreventXSSattacks.However,triplebracesbypassescaping,renderingHTMLas-is.Thisshouldbeusedsparinglyandonlywithfullytrusteddata.Acceptablecases

Selectingonlyneededcolumnsimprovesperformancebyreducingresourceusage.1.Fetchingallcolumnsincreasesmemory,network,andprocessingoverhead.2.Unnecessarydataretrievalpreventseffectiveindexuse,raisesdiskI/O,andslowsqueryexecution.3.Tooptimize,identifyrequi

TomockdependencieseffectivelyinLaravel,usedependencyinjectionforservices,shouldReceive()forfacades,andMockeryforcomplexcases.1.Forinjectedservices,use$this->instance()toreplacetherealclasswithamock.2.ForfacadeslikeMailorCache,useshouldReceive()tod
