From 12837212ca6dee06709af5733988e71ca79a6506 Mon Sep 17 00:00:00 2001 From: Michael Hoennig Date: Wed, 20 Nov 2024 15:24:40 +0100 Subject: [PATCH] add problem with Too Many Business-Rules Implemented in Controllers to README --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 308d5c51..38defd3b 100644 --- a/README.md +++ b/README.md @@ -575,7 +575,7 @@ that and creates too many (grant- and role-) rows and too even tables which coul The basic idea is always to always have a fixed set of ordered role-types which apply for all DB-tables under RBAC, e.g. OWNER>ADMIN>AGENT\[>PROXY?\]>TENENT>REFERRER. -Grants between these for the same DB-row would be implicit by order comparision. +Grants between these for the same DB-row would be implicit by order comparison. This way we would get rid of all explicit grants within the same DB-row and would not need the `rbac.role` table anymore. We would also reduce the depth of the expensive recursive CTE-query. @@ -591,6 +591,12 @@ E.g. the uuid of the target main object is often taken from an uuid of a sub-sub (For now, use `StrictMapper` to avoid this, for the case it happens.) +### Too Many Business-Rules Implemented in Controllers + +Some REST-Controllers implement too much code for business-roles. +This should be extracted to services. + + ## How To ... ### How to Configure .pgpass for the Default PostgreSQL Database?