Post -> comments (3). One comment is already deleted. Post::first()->delete(); After call this all 3 comments has deleted_at set in one moment. Is this how it should works? Restoring post cause restore all 3 comments, i think should only 2 comment which was deleted with post.

Context

I have an /admin dashboard to control what to hide and what to show for the frontend. My Job model's relationships:

Job -> belongsTo: Category Job -> belongsTo: Company

In my admin/jobs/index.blade view I list the jobs with links to $job->company and $job->category, but because I soft deleted a company or category, it gives route error.

Question

How do I query for a trashed relationship so I can still see it?

I'm querying for jobs correctly, but the relationships aren't found, is there a way to include them even if soft deleted?

/**
 * Display a listing of the resource.
 *
 * @return \Illuminate\View\View
 */
public function index() : View
{
    $jobs = Job::latest()->withTrashed()->paginate(20);

    return view('admin.jobs.index')->with(compact('jobs'));
}

No rush. And thanks for this package, works great!! 😎

On belongs to many relation, a bad pivot key name is used to find the good relation

https://github.com/Askedio/laravel5-soft-cascade/blob/d0424664f3f1e0b9a0c823cf1d2cf6bd00884e6d/src/SoftCascade.php#L146

Changing getQualifiedForeignPivotKeyName with getRelatedPivotKeyName works for me :)

softcascade should not change deleted_at timestamps of already deleted childmodels, becaus this could break unique Indexes on pivot tables. E.g. i had a parent model wich contains n child models at position 0..n. to ensure each position is only user once for every parent i created a unique index over the columns parent.id,position and deleted_at in the pivot table. when deleteing the parent Model softcascade tries to change all of the related childmodels to the same deleted_at timestamp, which will not work with the unique index. As i can't see no use in changing all the timestamp of already deleted items, i made this PR Kind Regards Tom

First thank you for this great package!

As far as I can tell, when cascade-restoring a model, the updated_at column is changed which is a problem for my application. Is it a Laravel problem? Is it this package, and if so, is it the intended behaviour? And finally, is there a way to disable this behaviour?

Thank you in advance!

What will happen if I have used onDelete restrict while creating a relationship. Does this softDelete will raise and restrict that record from softdeleting?

I know there's already a PR created for this matter, but it needed further changes.

PHPUnit and Testbench need to be updated as well. Also, str_ and array_ helpers were removed from the core so the tests failed with a L6 installation.

In my system a Student is a User. After the following code a user was actually deleted. However, it took the students id and used it on the user table, thus, deleting the wrong user.

This is my controller's method

try {
            DB::transaction(function () use ($id) {
                Student::findOrFail($id)->delete();
            }, 5);
            return redirect()->action('StudentController@index');
        } catch (ModelNotFoundException $exception) {
            return redirect()->action('StudentController@index');
        }

This is my Student class

<?php

namespace App;

use Askedio\SoftCascade\Traits\SoftCascadeTrait;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\SoftDeletes;

class Student extends Model
{
    use SoftCascadeTrait;
    use SoftDeletes;
    protected $softCascade = ['user'];
    protected $dates = ['deleted_at'];
    public function user()
    {
        return $this->belongsTo('App\User');
    }
}

Am I missing anything?

• Laravel Soft Cacade Version: 5.5.15
• PHP Version: 7.1
• Database Driver & Version: MySQL Ver 14.14 Distrib 5.7.16 for osx10.11

Description

The model events (like deleting or deleted) are not fired during the soft cascade (not sure if this is intended behavior).

I want to use Observers to act on the models before they are soft deleted, but they don't get called since the events are not fired.

I am taking steps to upgrade my Laravel version, so if this is already solved (in case it isn't expected behavior) in the package's 5.6 and 5.7, that would be a relief.

Thanks for your time. Awesome package, by the way!

Steps to Reproduce

Create an Observer for a model that is going to be cascade (soft) deleted and then (soft) delete the parent model.

Edit: typo.

Code Example

ModelA.php

class ModelA extends Model
{
     use SoftDeletes;
     use SoftCascadeTrait;

     protected $dates = ['deleted_at'];

     protected $softCascade = [
         'children'
     ];

     public function children()
     {
          return $this->hasMany(ModelB::class);
     }
}

ModelB.php

{
     use SoftDeletes;

     protected $dates = ['deleted_at'];

     public function parent()
     {
          return $this->hasOne(ModelA::class);
     }
}

ModelBObserver.php

class ModelBObserver
{

    public function deleting(ModelB $model)
    {
        $model->name = 'Deleted Model';
        $model->save();
    }
}

In AppServiceProvider.php

public function boot() 
{
     ...
     ModelB::observe(ModelBObserver::class);
}

In a Test file:

/** @test **/
public function testEventsOnCascade()
{
     $modelA = new ModelA();
     $modelA->save();
     $modelA->refresh();

     $modelB = new ModelB();
     $modelB->parent_id = $modalA->id;
     $modelB->save();

     $modelA->refresh();
     $modelB->refresh();

     $modelA->delete();
     $modelB->refresh();

     $this->assertEquals('Deleted Model', $modelB->name);
}

The test fails.

Hi!, I have a "Issuer" model with a one-to-many relationship with "Branch", "Receivers", "Product", if I delete a "Issuer" the related models are correctly deleted in cascade, but, if I delete a "Branch" (which has a one-to-many relationship with "Phone", "Series") "Branch", "Phone", "Series" are deleted because they are dependent on "Branch" and also deletes the "Issuer" model, although "Issuer" and "Branch" have a relationship, how can I avoid that by eliminating a "Branch" the "Issuer" or some other relationship is not deleted?

On the 15th of February, Laravel 9 support was merged with #131 but no release was ever made. An issue was raised with the request to make a release tag #136 but it has gone un responded.

Is this package now considered abandoned? 4 months later no release has been created forcing users to either use the main branch which isn't the best or find an alternate package.

I see a closed topic about Laravel 9 support, but this package is the only one not letting me update to Laravel 9.

Here's the error:

  Problem 1
    - Root composer.json requires askedio/laravel-soft-cascade ^8.1 -> satisfiable by askedio/laravel-soft-cascade[8.1.0].
    - askedio/laravel-soft-cascade 8.1.0 requires illuminate/support ^7.0|^8.0 -> found illuminate/support[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

You can also try re-running composer require with an explicit version constraint, e.g. "composer require askedio/laravel-soft-cascade:*" to figure out if any version is installable, or "composer require askedio/laravel-soft-cascade:^2.1" if you know which you need.

Any ideas? Thanks!

Add behavior similar to SET NULL action. It will set relation column to NULL when referenced model is deleted.

For example

Class User extends Model {
  use SoftDeletes, SoftCascadeTrait;
  
  protected $softCascade = ['phone@setNull'];
  
  public function phone()
  {
    return $this->hasOne(Phone::class);
  }
}

Class Phone extends Model {
   use SoftDeletes;
  
  public function user()
  {
    return $this->belongsTo(User::class);
  }
}

Will set NULL in phones.user_id if user was soft deleted.

Description:

I have an application where users can create posts. I've given users the ability to delete posts which performs a soft delete on the record. In the following use case i restore records that I don't want.

• User creates 3 posts
• User deletes 1 of those posts which is soft deleted
• Admin deletes the user and it is softdeleted along with 2 more posts(cascading).
• Admin restores the user, but all 3 posts are restored.

Is there a way to only restore records that were done by the cascading soft delete.

Doing some testing with the softCascades and I delete a UserType Model with 9 relations. Some of those relations have 2-3 relations themselves, most have none. All relations/models have softDeletes added/enabled.

When I try deleting the vendor, it eventually dies out with Allocated memory exhausted. Currently its at 4GB, but there has to be a better/more efficient way? Or am wrong in thinking how this should work?

• Laravel Soft Cascade Version: 7.0.2-8.1.0

Description:

BlackDuck software highlights laravel-soft-cascade as library with unknown license. Same is reported by packagist.org ("There is no license information available for the latest version (8.1.0) of this package.")

Steps To Reproduce:

Visit packagist repository of the package: https://packagist.org/packages/askedio/laravel-soft-cascade#7.0.2 https://packagist.org/packages/askedio/laravel-soft-cascade

Solution:

According to https://getcomposer.org/doc/04-schema.md#license it should be added to composer.json. { "license": "MIT" }