However, when I delete a user ( User::destroy(2)) the rows for that user in the role_user table do not get deleted, which is causing redundant rows.ĮDIT: Grabbing the model and applying ->delete() also has the same effect. laravel eloquent protips php That Laravel’s documentation is rich in content no one can deny, but it does not mean that it has everything it can offer us. Now, I add a couple of users, and attach some roles - everything works fine.

Normally, you would use your database's foreign key constraints, adding an ON DELETE CASCADE rule to the foreign.

In order to delete a user record, you first have to delete all the records for that user from the registrations table. So as per the docs, I set my foreign keys to unsigned. 'In scenarios when you delete a parent record - say for example a blog post - you may want to also delete any comments associated with it as a form of self-maintenance of your data. You cannot delete a record from the user table because you have a relationship with the registrations table (registrationsuseridforeign). When a user delete from user table, all sessionrequests related to him want to delete. Since even the 'cascade' is not triggered, I 'set null' is not the problem. But deleting the cover picture, wont delete the gallery (for test purposes). $table->foreign('user_id')->references('id')->on('users')->onDelete('cascade') I have users table and sessionrequests table. Also, even the 'cascade' option doesn't work (only on the gallery table). Schema::create('role_user', function(Blueprint $table) Schema::create('roles', function(Blueprint $table) Schema::create('users', function(Blueprint $table) My migrations are setup as so (simplified): I have a many-to-many relationship between User & Role, with a role_user table.

Laravel eloquent delete cascade