Cascade delete and restore when using the Laravel or Lumen SoftDeletes feature.
| Laravel | laravel-soft-cascade | Lifecycle |
|---|---|---|
| ^5.5 | ^5.5 | January 24, 2017 |
| Bug fixes until January 2019 | ||
| Security fixes until June 2020 | ||
| ^5.6 | ^5.6 | February 7, 2018 |
| 6 months of bug fixes | ||
| 1 year of security | ||
| ^5.7 | ^5.7 | September 4, 2018 |
| 6 months of bug fixes | ||
| 1 year of security | ||
| ^5.8 | ^5.8 | February 26, 2019 |
| 6 months of bug fixes | ||
| 1 year of security |
If you enjoy features like MySQL cascade deleting but want to use Laravels SoftDeletes feature you'll need to do some extra steps to ensure your relations are properly deleted or restored.
This package is intended to replace those steps with a simple array that defines the relations you want to cascade.
Install with composer
composer require askedio/laravel-soft-cascade
From Laravel 5.5 onwards, it's possible to take advantage of auto-discovery of the service provider. For Laravel versions before 5.5, you must register the service provider in your config/app.php
Askedio\SoftCascade\Providers\GenericServiceProvider::class,
Lumen does not support the auto-discovery feature, you should manually add the provider.
Askedio\SoftCascade\Providers\LumenServiceProvider::class,
In your Model enable the trait and define $softCascade. Example.
use \Askedio\SoftCascade\Traits\SoftCascadeTrait;
protected $softCascade = ['profiles'];
For restricted relation use. Example.
use \Askedio\SoftCascade\Traits\SoftCascadeTrait;
protected $softCascade = ['addresses@restrict'];
$softCascade is an array of your relation names, in the example you'll see we've defined function profiles() for the relation.
Nested relations work by defining $softCascade in the related Model as you can see here.
After you've defined your relations you can simply trigger delete() or restore() on your Model and your relations will have the same task performed.
User::first()->delete();
User::withTrashed()->first()->restore();
It can also be used with query builder in this way because query builder listener is executed after query, we need to use transaction for rollback query on error due to restricted relationships
try {
DB::beginTransaction(); //Start db transaction for rollback query when error
User::limit(2)->delete();
User::withTrashed()->limit(2)->restore();
DB::commit(); //Commit the query
} catch (\Exception $e) {
DB::rollBack(); //Rollback the query
//Optional, if we need to continue execution only rollback transaction and save message on variable
throw new \Askedio\SoftCascade\Exceptions\SoftCascadeLogicException($e->getMessage());
}
- >=7.1.13
- MySQL
- PostgreSQL
- SQLite
- SQL Server
I have written some very basic tests, certainly more needs to be done here. If you find this useful please help by testing other databases or writing better unit tests because I must move on.
I will be using this with MySQL in a new API so any issues I find related to my use will be resolved. If you find an issue with MySQL please report it and I will fix it.
If you are using another database and have issues please contribute by submitting a pull request. I do not have time to test this with other database but assume all would work.