Prevent permissionset foreign key constraint
This commit is contained in:
parent
9a4128a5c8
commit
56db5a29c4
1 changed files with 9 additions and 0 deletions
|
@ -57,8 +57,17 @@ class ExpireAndRemoveUsers
|
||||||
DBA::delete('contact', ['nurl' => $self['nurl'], 'self' => false]);
|
DBA::delete('contact', ['nurl' => $self['nurl'], 'self' => false]);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
// We have to delete photo entries by hand because otherwise the photo data won't be deleted
|
||||||
Photo::delete(['uid' => $user['uid']]);
|
Photo::delete(['uid' => $user['uid']]);
|
||||||
|
|
||||||
|
// These tables contain the permissionset which will also be deleted when a user is deleted.
|
||||||
|
// It seems that sometimes the system wants to delete the records in the wrong order.
|
||||||
|
// So when the permissionset is deleted and these tables are still filled then an error is thrown.
|
||||||
|
// So we now delete them before all other user related entries are deleted.
|
||||||
|
DBA::delete('item', ['uid' => $user['uid']]);
|
||||||
|
DBA::delete('post-user', ['uid' => $user['uid']]);
|
||||||
|
DBA::delete('profile_field', ['uid' => $user['uid']]);
|
||||||
|
|
||||||
DBA::delete('user', ['uid' => $user['uid']]);
|
DBA::delete('user', ['uid' => $user['uid']]);
|
||||||
}
|
}
|
||||||
DBA::close($users);
|
DBA::close($users);
|
||||||
|
|
Loading…
Reference in a new issue