Timeline for How to completely avoid business logic in DAL?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2024 at 5:37 | comment | added | Brad | Main problem I have is complex access permissions. Weather or not a user has access to something is business logic but the optimal way to handle is is if the query just checks access by joining tables and filtering results directly from access permissions stored. I guess that's your point tho right? Once permissions are stored the business logic part is over and the DAL is just responding to it. It does require the current users details however and has Logic to adjust the query based on the user context. | |
| Mar 14, 2014 at 21:42 | comment | added | Robert Goldwein | That's very clear, thanks a lot. I didn't see the forest for the trees. | |
| Mar 14, 2014 at 21:38 | vote | accept | Robert Goldwein | ||
| Mar 14, 2014 at 21:31 | history | answered | sea-rob | CC BY-SA 3.0 |