How to soft delete related records when soft deleting a parent record in Laravel?











up vote
12
down vote

favorite
1












I have this invoices table that which has the following structure



id | name | amount | deleted_at
2 iMac 1500 | NULL


and a payments table with the following structure



id | invoice_id | amount | deleted_at
2 2 1000 | NULL


Invoice Model



class Invoice extends Model {

use SoftDeletes;

}


here's the code to delete the invoice



public function cance(Request $request,$id)
{
$record = Invoice::findOrFail($id);
$record->delete();
return response()->json([
'success' => 'OK',
]);
}


Payments model



class Payment extends Model {

use SoftDeletes;

}


The softDelete on Invoice table works perfectly but its related records (payments) still exists.How do I delete them using softDelete?










share|improve this question


























    up vote
    12
    down vote

    favorite
    1












    I have this invoices table that which has the following structure



    id | name | amount | deleted_at
    2 iMac 1500 | NULL


    and a payments table with the following structure



    id | invoice_id | amount | deleted_at
    2 2 1000 | NULL


    Invoice Model



    class Invoice extends Model {

    use SoftDeletes;

    }


    here's the code to delete the invoice



    public function cance(Request $request,$id)
    {
    $record = Invoice::findOrFail($id);
    $record->delete();
    return response()->json([
    'success' => 'OK',
    ]);
    }


    Payments model



    class Payment extends Model {

    use SoftDeletes;

    }


    The softDelete on Invoice table works perfectly but its related records (payments) still exists.How do I delete them using softDelete?










    share|improve this question
























      up vote
      12
      down vote

      favorite
      1









      up vote
      12
      down vote

      favorite
      1






      1





      I have this invoices table that which has the following structure



      id | name | amount | deleted_at
      2 iMac 1500 | NULL


      and a payments table with the following structure



      id | invoice_id | amount | deleted_at
      2 2 1000 | NULL


      Invoice Model



      class Invoice extends Model {

      use SoftDeletes;

      }


      here's the code to delete the invoice



      public function cance(Request $request,$id)
      {
      $record = Invoice::findOrFail($id);
      $record->delete();
      return response()->json([
      'success' => 'OK',
      ]);
      }


      Payments model



      class Payment extends Model {

      use SoftDeletes;

      }


      The softDelete on Invoice table works perfectly but its related records (payments) still exists.How do I delete them using softDelete?










      share|improve this question













      I have this invoices table that which has the following structure



      id | name | amount | deleted_at
      2 iMac 1500 | NULL


      and a payments table with the following structure



      id | invoice_id | amount | deleted_at
      2 2 1000 | NULL


      Invoice Model



      class Invoice extends Model {

      use SoftDeletes;

      }


      here's the code to delete the invoice



      public function cance(Request $request,$id)
      {
      $record = Invoice::findOrFail($id);
      $record->delete();
      return response()->json([
      'success' => 'OK',
      ]);
      }


      Payments model



      class Payment extends Model {

      use SoftDeletes;

      }


      The softDelete on Invoice table works perfectly but its related records (payments) still exists.How do I delete them using softDelete?







      php laravel laravel-5 eloquent soft-delete






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 23 '15 at 5:32









      user3407278

      460928




      460928
























          3 Answers
          3






          active

          oldest

          votes

















          up vote
          11
          down vote



          accepted










          Eloquent doesn't provide automated deletion of related objects, therefore you'll need to write some code yourself. Luckily, it's pretty simple.



          Eloquent models fire different events in different stages of model's life-cycle like creating, created, deleting, deleted etc. - you can read more about it here: http://laravel.com/docs/5.1/eloquent#events. What you need is a listener that will run when deleted event is fired - this listener should then delete all related objects.



          You can register model listeners in your model's boot() method. The listener should iterate through all payments for the invoice being deleted and should delete them one by one. Bulk delete won't work here as it would execute SQL query directly bypassing model events.



          This will do the trick:



          class MyModel extends Model {
          protected static function boot() {
          parent::boot();

          static::deleted(function ($invoice) {
          $invoice->payments()->delete();
          });
          }
          }





          share|improve this answer























          • Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
            – user3407278
            Aug 23 '15 at 7:07










          • Fixed, the function was missing the static modifier
            – jedrzej.kurylo
            Aug 23 '15 at 7:10










          • That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
            – user3407278
            Aug 23 '15 at 7:18










          • You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
            – jedrzej.kurylo
            Aug 23 '15 at 7:20










          • thank you! @jedrzej.kurylo !!
            – user3407278
            Aug 23 '15 at 7:30


















          up vote
          9
          down vote













          You can go one of 2 ways with this.



          The simplest way would be to override Eloquents delete() method and include the related models as well e.g.:



          public function delete()
          {
          $this->payments()->delete();
          return parent::delete();
          }


          The above method should work just find but it seems a little bit dirty and I'd say it's not the preferred method within the community.



          The cleaner way (IMO) would be to tap into Eloquents events e.g.:



          public static function boot()
          {
          parent::boot();

          static::deleting(function($invoice) {
          $invoice->payments()->delete();

          });
          }


          Either (but not both) of the above methods would go in your Invoice model.
          Also, I'm assuming that you have your relationships set up in your model, however, I'm not sure if you allow multiple payments for one invoice. Either way you might need to change the payments() in the examples to whatever you've named the relationship in your invoice model.



          Hope this helps!






          share|improve this answer























          • Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
            – jedrzej.kurylo
            Aug 23 '15 at 6:38










          • You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
            – jedrzej.kurylo
            Aug 23 '15 at 6:54










          • @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
            – Ross Wilson
            Aug 23 '15 at 7:30










          • True, just checked the code. Good to know for the future :)
            – jedrzej.kurylo
            Aug 23 '15 at 7:43










          • does it guarantee transaction @RossWilson
            – Tomonso Ejang
            Jul 20 at 8:07




















          up vote
          4
          down vote













          I know you asked this question a long time ago but I found this package to be very simple and straightforward:



          https://github.com/Askedio/laravel5-soft-cascade



          Or you can use this package it's useful too:



          https://github.com/michaeldyrynda/laravel-cascade-soft-deletes



          Remember to install the right version depending on your laravel version.



          You must install it via composer:



           composer require askedio/laravel5-soft-cascade ^version


          In second package:



           composer require iatstuti/laravel-cascade-soft-deletes


          Register the service provider in your config/app.php.



          you can read the docs on the GitHub page.



          If you delete a record this package recognizes all of its children and soft-delete them as well.



          If you have another relationship in your child model use its trait in that model as well. its so much easier than doing it manually.



          The second package has the benefit of deleting grandchildren of the model. in some cases, I say its a better approach.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32163509%2fhow-to-soft-delete-related-records-when-soft-deleting-a-parent-record-in-laravel%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            11
            down vote



            accepted










            Eloquent doesn't provide automated deletion of related objects, therefore you'll need to write some code yourself. Luckily, it's pretty simple.



            Eloquent models fire different events in different stages of model's life-cycle like creating, created, deleting, deleted etc. - you can read more about it here: http://laravel.com/docs/5.1/eloquent#events. What you need is a listener that will run when deleted event is fired - this listener should then delete all related objects.



            You can register model listeners in your model's boot() method. The listener should iterate through all payments for the invoice being deleted and should delete them one by one. Bulk delete won't work here as it would execute SQL query directly bypassing model events.



            This will do the trick:



            class MyModel extends Model {
            protected static function boot() {
            parent::boot();

            static::deleted(function ($invoice) {
            $invoice->payments()->delete();
            });
            }
            }





            share|improve this answer























            • Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
              – user3407278
              Aug 23 '15 at 7:07










            • Fixed, the function was missing the static modifier
              – jedrzej.kurylo
              Aug 23 '15 at 7:10










            • That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
              – user3407278
              Aug 23 '15 at 7:18










            • You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
              – jedrzej.kurylo
              Aug 23 '15 at 7:20










            • thank you! @jedrzej.kurylo !!
              – user3407278
              Aug 23 '15 at 7:30















            up vote
            11
            down vote



            accepted










            Eloquent doesn't provide automated deletion of related objects, therefore you'll need to write some code yourself. Luckily, it's pretty simple.



            Eloquent models fire different events in different stages of model's life-cycle like creating, created, deleting, deleted etc. - you can read more about it here: http://laravel.com/docs/5.1/eloquent#events. What you need is a listener that will run when deleted event is fired - this listener should then delete all related objects.



            You can register model listeners in your model's boot() method. The listener should iterate through all payments for the invoice being deleted and should delete them one by one. Bulk delete won't work here as it would execute SQL query directly bypassing model events.



            This will do the trick:



            class MyModel extends Model {
            protected static function boot() {
            parent::boot();

            static::deleted(function ($invoice) {
            $invoice->payments()->delete();
            });
            }
            }





            share|improve this answer























            • Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
              – user3407278
              Aug 23 '15 at 7:07










            • Fixed, the function was missing the static modifier
              – jedrzej.kurylo
              Aug 23 '15 at 7:10










            • That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
              – user3407278
              Aug 23 '15 at 7:18










            • You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
              – jedrzej.kurylo
              Aug 23 '15 at 7:20










            • thank you! @jedrzej.kurylo !!
              – user3407278
              Aug 23 '15 at 7:30













            up vote
            11
            down vote



            accepted







            up vote
            11
            down vote



            accepted






            Eloquent doesn't provide automated deletion of related objects, therefore you'll need to write some code yourself. Luckily, it's pretty simple.



            Eloquent models fire different events in different stages of model's life-cycle like creating, created, deleting, deleted etc. - you can read more about it here: http://laravel.com/docs/5.1/eloquent#events. What you need is a listener that will run when deleted event is fired - this listener should then delete all related objects.



            You can register model listeners in your model's boot() method. The listener should iterate through all payments for the invoice being deleted and should delete them one by one. Bulk delete won't work here as it would execute SQL query directly bypassing model events.



            This will do the trick:



            class MyModel extends Model {
            protected static function boot() {
            parent::boot();

            static::deleted(function ($invoice) {
            $invoice->payments()->delete();
            });
            }
            }





            share|improve this answer














            Eloquent doesn't provide automated deletion of related objects, therefore you'll need to write some code yourself. Luckily, it's pretty simple.



            Eloquent models fire different events in different stages of model's life-cycle like creating, created, deleting, deleted etc. - you can read more about it here: http://laravel.com/docs/5.1/eloquent#events. What you need is a listener that will run when deleted event is fired - this listener should then delete all related objects.



            You can register model listeners in your model's boot() method. The listener should iterate through all payments for the invoice being deleted and should delete them one by one. Bulk delete won't work here as it would execute SQL query directly bypassing model events.



            This will do the trick:



            class MyModel extends Model {
            protected static function boot() {
            parent::boot();

            static::deleted(function ($invoice) {
            $invoice->payments()->delete();
            });
            }
            }






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 10 at 22:15









            asachanfbd

            1,0881923




            1,0881923










            answered Aug 23 '15 at 6:35









            jedrzej.kurylo

            25.1k54664




            25.1k54664












            • Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
              – user3407278
              Aug 23 '15 at 7:07










            • Fixed, the function was missing the static modifier
              – jedrzej.kurylo
              Aug 23 '15 at 7:10










            • That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
              – user3407278
              Aug 23 '15 at 7:18










            • You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
              – jedrzej.kurylo
              Aug 23 '15 at 7:20










            • thank you! @jedrzej.kurylo !!
              – user3407278
              Aug 23 '15 at 7:30


















            • Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
              – user3407278
              Aug 23 '15 at 7:07










            • Fixed, the function was missing the static modifier
              – jedrzej.kurylo
              Aug 23 '15 at 7:10










            • That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
              – user3407278
              Aug 23 '15 at 7:18










            • You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
              – jedrzej.kurylo
              Aug 23 '15 at 7:20










            • thank you! @jedrzej.kurylo !!
              – user3407278
              Aug 23 '15 at 7:30
















            Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
            – user3407278
            Aug 23 '15 at 7:07




            Doesn't work! FatalErrorException in Invoice.php line 18: Cannot make static method IlluminateDatabaseEloquentModel::boot() non static in class AppModelsInvoice
            – user3407278
            Aug 23 '15 at 7:07












            Fixed, the function was missing the static modifier
            – jedrzej.kurylo
            Aug 23 '15 at 7:10




            Fixed, the function was missing the static modifier
            – jedrzej.kurylo
            Aug 23 '15 at 7:10












            That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
            – user3407278
            Aug 23 '15 at 7:18




            That worked beautifully! Thanks a lot! Does this cause any performance issues when soft deleting say about 100 records?
            – user3407278
            Aug 23 '15 at 7:18












            You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
            – jedrzej.kurylo
            Aug 23 '15 at 7:20




            You have to fetch all of them and then save each of them, so it's additional 101 queries... In such case you could set the deleted_at manually for related models, this will be less clean but will run only one SQL query. I'll update the answer in a second
            – jedrzej.kurylo
            Aug 23 '15 at 7:20












            thank you! @jedrzej.kurylo !!
            – user3407278
            Aug 23 '15 at 7:30




            thank you! @jedrzej.kurylo !!
            – user3407278
            Aug 23 '15 at 7:30












            up vote
            9
            down vote













            You can go one of 2 ways with this.



            The simplest way would be to override Eloquents delete() method and include the related models as well e.g.:



            public function delete()
            {
            $this->payments()->delete();
            return parent::delete();
            }


            The above method should work just find but it seems a little bit dirty and I'd say it's not the preferred method within the community.



            The cleaner way (IMO) would be to tap into Eloquents events e.g.:



            public static function boot()
            {
            parent::boot();

            static::deleting(function($invoice) {
            $invoice->payments()->delete();

            });
            }


            Either (but not both) of the above methods would go in your Invoice model.
            Also, I'm assuming that you have your relationships set up in your model, however, I'm not sure if you allow multiple payments for one invoice. Either way you might need to change the payments() in the examples to whatever you've named the relationship in your invoice model.



            Hope this helps!






            share|improve this answer























            • Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
              – jedrzej.kurylo
              Aug 23 '15 at 6:38










            • You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
              – jedrzej.kurylo
              Aug 23 '15 at 6:54










            • @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
              – Ross Wilson
              Aug 23 '15 at 7:30










            • True, just checked the code. Good to know for the future :)
              – jedrzej.kurylo
              Aug 23 '15 at 7:43










            • does it guarantee transaction @RossWilson
              – Tomonso Ejang
              Jul 20 at 8:07

















            up vote
            9
            down vote













            You can go one of 2 ways with this.



            The simplest way would be to override Eloquents delete() method and include the related models as well e.g.:



            public function delete()
            {
            $this->payments()->delete();
            return parent::delete();
            }


            The above method should work just find but it seems a little bit dirty and I'd say it's not the preferred method within the community.



            The cleaner way (IMO) would be to tap into Eloquents events e.g.:



            public static function boot()
            {
            parent::boot();

            static::deleting(function($invoice) {
            $invoice->payments()->delete();

            });
            }


            Either (but not both) of the above methods would go in your Invoice model.
            Also, I'm assuming that you have your relationships set up in your model, however, I'm not sure if you allow multiple payments for one invoice. Either way you might need to change the payments() in the examples to whatever you've named the relationship in your invoice model.



            Hope this helps!






            share|improve this answer























            • Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
              – jedrzej.kurylo
              Aug 23 '15 at 6:38










            • You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
              – jedrzej.kurylo
              Aug 23 '15 at 6:54










            • @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
              – Ross Wilson
              Aug 23 '15 at 7:30










            • True, just checked the code. Good to know for the future :)
              – jedrzej.kurylo
              Aug 23 '15 at 7:43










            • does it guarantee transaction @RossWilson
              – Tomonso Ejang
              Jul 20 at 8:07















            up vote
            9
            down vote










            up vote
            9
            down vote









            You can go one of 2 ways with this.



            The simplest way would be to override Eloquents delete() method and include the related models as well e.g.:



            public function delete()
            {
            $this->payments()->delete();
            return parent::delete();
            }


            The above method should work just find but it seems a little bit dirty and I'd say it's not the preferred method within the community.



            The cleaner way (IMO) would be to tap into Eloquents events e.g.:



            public static function boot()
            {
            parent::boot();

            static::deleting(function($invoice) {
            $invoice->payments()->delete();

            });
            }


            Either (but not both) of the above methods would go in your Invoice model.
            Also, I'm assuming that you have your relationships set up in your model, however, I'm not sure if you allow multiple payments for one invoice. Either way you might need to change the payments() in the examples to whatever you've named the relationship in your invoice model.



            Hope this helps!






            share|improve this answer














            You can go one of 2 ways with this.



            The simplest way would be to override Eloquents delete() method and include the related models as well e.g.:



            public function delete()
            {
            $this->payments()->delete();
            return parent::delete();
            }


            The above method should work just find but it seems a little bit dirty and I'd say it's not the preferred method within the community.



            The cleaner way (IMO) would be to tap into Eloquents events e.g.:



            public static function boot()
            {
            parent::boot();

            static::deleting(function($invoice) {
            $invoice->payments()->delete();

            });
            }


            Either (but not both) of the above methods would go in your Invoice model.
            Also, I'm assuming that you have your relationships set up in your model, however, I'm not sure if you allow multiple payments for one invoice. Either way you might need to change the payments() in the examples to whatever you've named the relationship in your invoice model.



            Hope this helps!







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Aug 23 '15 at 7:00

























            answered Aug 23 '15 at 6:35









            Ross Wilson

            15.3k22539




            15.3k22539












            • Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
              – jedrzej.kurylo
              Aug 23 '15 at 6:38










            • You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
              – jedrzej.kurylo
              Aug 23 '15 at 6:54










            • @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
              – Ross Wilson
              Aug 23 '15 at 7:30










            • True, just checked the code. Good to know for the future :)
              – jedrzej.kurylo
              Aug 23 '15 at 7:43










            • does it guarantee transaction @RossWilson
              – Tomonso Ejang
              Jul 20 at 8:07




















            • Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
              – jedrzej.kurylo
              Aug 23 '15 at 6:38










            • You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
              – jedrzej.kurylo
              Aug 23 '15 at 6:54










            • @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
              – Ross Wilson
              Aug 23 '15 at 7:30










            • True, just checked the code. Good to know for the future :)
              – jedrzej.kurylo
              Aug 23 '15 at 7:43










            • does it guarantee transaction @RossWilson
              – Tomonso Ejang
              Jul 20 at 8:07


















            Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
            – jedrzej.kurylo
            Aug 23 '15 at 6:38




            Calling delete() on payments relation directly will bypass the model and won't trigger the SoftDelete on related models. They will be removed from the database. In order to make thek soft-deleted you need to call delete() on each of related models.
            – jedrzej.kurylo
            Aug 23 '15 at 6:38












            You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
            – jedrzej.kurylo
            Aug 23 '15 at 6:54




            You are also missing the return statement in your overridden delete method - it should do "return parent::delete();", otherwise you lose the value that would be returned from delete() if you hadn't overwritten it.
            – jedrzej.kurylo
            Aug 23 '15 at 6:54












            @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
            – Ross Wilson
            Aug 23 '15 at 7:30




            @jedrzej.kurylo, I've just tested to make sure and YES you can use soft delete on a relationship!
            – Ross Wilson
            Aug 23 '15 at 7:30












            True, just checked the code. Good to know for the future :)
            – jedrzej.kurylo
            Aug 23 '15 at 7:43




            True, just checked the code. Good to know for the future :)
            – jedrzej.kurylo
            Aug 23 '15 at 7:43












            does it guarantee transaction @RossWilson
            – Tomonso Ejang
            Jul 20 at 8:07






            does it guarantee transaction @RossWilson
            – Tomonso Ejang
            Jul 20 at 8:07












            up vote
            4
            down vote













            I know you asked this question a long time ago but I found this package to be very simple and straightforward:



            https://github.com/Askedio/laravel5-soft-cascade



            Or you can use this package it's useful too:



            https://github.com/michaeldyrynda/laravel-cascade-soft-deletes



            Remember to install the right version depending on your laravel version.



            You must install it via composer:



             composer require askedio/laravel5-soft-cascade ^version


            In second package:



             composer require iatstuti/laravel-cascade-soft-deletes


            Register the service provider in your config/app.php.



            you can read the docs on the GitHub page.



            If you delete a record this package recognizes all of its children and soft-delete them as well.



            If you have another relationship in your child model use its trait in that model as well. its so much easier than doing it manually.



            The second package has the benefit of deleting grandchildren of the model. in some cases, I say its a better approach.






            share|improve this answer



























              up vote
              4
              down vote













              I know you asked this question a long time ago but I found this package to be very simple and straightforward:



              https://github.com/Askedio/laravel5-soft-cascade



              Or you can use this package it's useful too:



              https://github.com/michaeldyrynda/laravel-cascade-soft-deletes



              Remember to install the right version depending on your laravel version.



              You must install it via composer:



               composer require askedio/laravel5-soft-cascade ^version


              In second package:



               composer require iatstuti/laravel-cascade-soft-deletes


              Register the service provider in your config/app.php.



              you can read the docs on the GitHub page.



              If you delete a record this package recognizes all of its children and soft-delete them as well.



              If you have another relationship in your child model use its trait in that model as well. its so much easier than doing it manually.



              The second package has the benefit of deleting grandchildren of the model. in some cases, I say its a better approach.






              share|improve this answer

























                up vote
                4
                down vote










                up vote
                4
                down vote









                I know you asked this question a long time ago but I found this package to be very simple and straightforward:



                https://github.com/Askedio/laravel5-soft-cascade



                Or you can use this package it's useful too:



                https://github.com/michaeldyrynda/laravel-cascade-soft-deletes



                Remember to install the right version depending on your laravel version.



                You must install it via composer:



                 composer require askedio/laravel5-soft-cascade ^version


                In second package:



                 composer require iatstuti/laravel-cascade-soft-deletes


                Register the service provider in your config/app.php.



                you can read the docs on the GitHub page.



                If you delete a record this package recognizes all of its children and soft-delete them as well.



                If you have another relationship in your child model use its trait in that model as well. its so much easier than doing it manually.



                The second package has the benefit of deleting grandchildren of the model. in some cases, I say its a better approach.






                share|improve this answer














                I know you asked this question a long time ago but I found this package to be very simple and straightforward:



                https://github.com/Askedio/laravel5-soft-cascade



                Or you can use this package it's useful too:



                https://github.com/michaeldyrynda/laravel-cascade-soft-deletes



                Remember to install the right version depending on your laravel version.



                You must install it via composer:



                 composer require askedio/laravel5-soft-cascade ^version


                In second package:



                 composer require iatstuti/laravel-cascade-soft-deletes


                Register the service provider in your config/app.php.



                you can read the docs on the GitHub page.



                If you delete a record this package recognizes all of its children and soft-delete them as well.



                If you have another relationship in your child model use its trait in that model as well. its so much easier than doing it manually.



                The second package has the benefit of deleting grandchildren of the model. in some cases, I say its a better approach.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited May 12 at 12:48

























                answered Apr 18 at 12:50









                Salar Bahador

                4251313




                4251313






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f32163509%2fhow-to-soft-delete-related-records-when-soft-deleting-a-parent-record-in-laravel%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    鏡平學校

                    ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                    Why https connections are so slow when debugging (stepping over) in Java?