laravel delete model with all relations

bump

If you're using MySQL you can add 'ON DELETE CASCADE' to your foreign key. This will automatically delete any records that reference the parent when the parent is deleted. If your using Laravel's migrations add

$table->foreign('fk_id')->references('id')->on('table')->onDelete('cascade');

to your foreign key definition.

You can also add a delete method to your model and delete your relationships first then let the model complete the delete operation.

public function delete() {
    $this->checks()->delete();
    $this->results()->delete();
    parent::delete();
}

or have a look at Eloquent Events and specifically the deleting or deleted events.

@ctroms

Using the code you posted results in the same problem as before, only the main model gets deleted. The two related ones aren't deleted.

@jaheller Which code is not working the delete method in the model or the onDelete('cascade') method.

@ctroms

I updated first post.

@jaheller Try to change your boot method to

protected static function boot() {
    parent::boot();
    
    static::deleting(function($check) {
        $check->checks()->delete();
        $check->results()->delete();
    });
}

Since these relationships are on this model you shouldn't need to iterate over each one. Change your event to deleting rather than deleted.

@ctroms

This doesn't work too. Only the check is deleted, not the related items.

@jaheller Sorry. I didn't notice last night but I believe the issue is in your original query. Eloquent's events are not fired when you use a where constraint. In order to use the model event you would have to pull it into memory first . Leave your boot method and adjust your query to the following and it should work.

$checks = Check::where('created_at','<=', Carbon::now()->subHours(3))
    ->each(function($check) {
        $check->delete();
    });

I would still suggest letting MySQL handle this with a cascade if you are in fact using MySQL.

delete cascade on the database only works if actually removing the model, but what about soft deletes?

I add this observer to the model, and it deletes related models, as @ctroms suggested

    //observe this model being deleted and delete the child events
    public static function boot ()
    {
        parent::boot();

        self::deleting(function (Campaign $campaign) {

            foreach ($campaign->events as $event)
            {
                $event->delete();
            }
        });
    }

a campaign has many events, and an event has many shifts, and shifts have many activities - all have to be set soft deleted

so, in the Event model;

    //observe this model being deleted and delete the child activities
    public static function boot ()
    {
        parent::boot();

        self::deleting(function (CampaignEvent $event) {

            foreach ($event->shifts as $shift)
            {
                $shift->delete();
            }
        });
    }

and then similarly in the Shift model.

here, delete campaign -> delete all events ->delete all shifts

but of course it works just as well if I delete a single event - it automatically cascades to the shifts.

@Snapey Nice solution and good point on soft deletes. I was, possibly incorrectly, making assumptions.