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)

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

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

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

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.
