Implementing Soft Deletes on Eloquent Models in Laravel?
Jul 04, 2025 am 02:44 AMTo implement soft deletes in Laravel, use the SoftDeletes trait and add the deleted_at column to your table. First, include use Illuminate\Database\Eloquent\SoftDeletes; in your model and apply the trait inside the class. Second, call $table->softDeletes(); in your migration to create the deleted_at column. Third, run php artisan migrate to apply the changes. With this setup, calling delete() will set the deleted_at timestamp instead of removing the record. To query soft-deleted records, use withTrashed() to include them or onlyTrashed() to retrieve only deleted entries. To restore a record, call restore() on the soft-deleted instance. Keep in mind that relationships aren't automatically cascaded, performance may be impacted without indexing deleted_at, and storage can grow due to accumulated soft-deleted data. Use forceDelete() carefully as it permanently removes records.
When you're working with Laravel and want to avoid permanently deleting records from your database, implementing soft deletes on Eloquent models is the standard approach. Laravel makes this pretty straightforward — as long as you know how to set it up properly.

What Soft Deletes Do in Laravel
In short, soft deletes don’t actually remove a record from the database. Instead, they set a deleted_at
timestamp when a model is "deleted." This allows you to keep data intact while treating it as inactive or removed from the user's perspective.

Laravel provides a built-in SoftDeletes
trait that handles most of the logic for you. Once enabled, methods like delete()
won't remove the record from the database but will update the deleted_at
column instead.
Setting Up Soft Deletes in Your Model
To enable soft deletes for a model:

Use the SoftDeletes trait
In your model file, adduse Illuminate\Database\Eloquent\SoftDeletes;
at the top and includeuse SoftDeletes;
inside the model class.Add deleted_at column to your table
When creating or updating a migration for the corresponding table, make sure to call$table->softDeletes();
. It adds a nullabledeleted_at
column using thetimestamp
type.Run your migrations
If you’re modifying an existing table, create a new migration to add the column and runphp artisan migrate
.
Once done, any call to $model->delete()
will mark it as deleted without removing it from the database.
Querying Models With Soft Deletes
By default, Laravel automatically excludes soft-deleted records when querying models that use the SoftDeletes
trait. But there are times you may want to include or retrieve them explicitly.
-
Use
withTrashed()
to include soft-deleted records:User::withTrashed()->find(1);
Use
onlyTrashed()
to get only soft-deleted records:User::onlyTrashed()->get();
To restore a soft-deleted record:
$user = User::onlyTrashed()->find(1); $user->restore();
These tools help manage data recovery or implement admin interfaces where viewing deleted entries matters.
Things to Watch Out For
While soft deletes are convenient, they can lead to issues if not handled carefully.
- Relationships: By default, related models aren’t soft-deleted along with the parent. You’ll need to manually handle cascading behavior or use packages like
laravel-cascades-soft-deletes
if needed. - Performance: Large tables with many soft-deleted rows might slow down queries unless you index the
deleted_at
column (which is usually a good idea). - Data cleanup: Since nothing gets truly deleted, old soft-deleted records can pile up. Consider scheduled cleanups or archival strategies if storage becomes a concern.
You should also be cautious when using forceDelete()
— it bypasses soft delete entirely and removes the record permanently.
That’s basically how soft deletes work in Laravel. It’s not complicated once you understand the setup and query handling, but it does require attention to detail, especially when dealing with relationships or performance.
The above is the detailed content of Implementing Soft Deletes on Eloquent Models in Laravel?. 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)

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.

The core of handling HTTP requests and responses in Laravel is to master the acquisition of request data, response return and file upload. 1. When receiving request data, you can inject the Request instance through type prompts and use input() or magic methods to obtain fields, and combine validate() or form request classes for verification; 2. Return response supports strings, views, JSON, responses with status codes and headers and redirect operations; 3. When processing file uploads, you need to use the file() method and store() to store files. Before uploading, you should verify the file type and size, and the storage path can be saved to the database.

The most common way to generate a named route in Laravel is to use the route() helper function, which automatically matches the path based on the route name and handles parameter binding. 1. Pass the route name and parameters in the controller or view, such as route('user.profile',['id'=>1]); 2. When multiple parameters, you only need to pass the array, and the order does not affect the matching, such as route('user.post.show',['id'=>1,'postId'=>10]); 3. Links can be directly embedded in the Blade template, such as viewing information; 4. When optional parameters are not provided, they are not displayed, such as route('user.post',
