feat: Implementiere kaskadierende Löschung für die User-Entität im UserRepository

- Überriding der DeleteAsync-Methode hinzugefügt, um verwandte ModuleOfUser- und GroupOfUser-Entitäten zu behandeln.
- Sicherstellung der Entfernung verwandter Datensätze bei der Löschung eines Benutzers.
- TODO-Kommentar hinzugefügt, um zu empfehlen, .OnDelete(DeleteBehavior.ClientCascade) im DbContext für ein verbessertes Verhalten zu verwenden.
This commit is contained in:
Developer 02
2024-10-29 16:13:58 +01:00
parent ae14f5842e
commit 622cb1f702
2 changed files with 30 additions and 1 deletions

View File

@@ -32,4 +32,19 @@ namespace DigitalData.UserManager.Infrastructure
return modelBuilder;
}
}
}
}
//TODO: DeleteBehavior.Restrict (see example comment below) is not working, probably due to table relationships. Because it tries to delete, for example, User first and then GroupOfUser. However, since GroupOfUser is not deleted while Users is deleted, the error is thrown because of the table relationship. Apply this approach after finding the solution.
/*
modelBuilder.Entity<User>()
.HasMany<GroupOfUser>()
.WithOne(gou => gou.User)
.HasForeignKey(gou => gou.UserId)
.OnDelete(DeleteBehavior.ClientCascade);
modelBuilder.Entity<User>()
.HasMany<ModuleOfUser>()
.WithOne(mou => mou.User)
.HasForeignKey(mou => mou.UserId)
.OnDelete(DeleteBehavior.ClientCascade);
*/