Ruderverein-Donau-Linz/rowt
1
1
Fork 1
Code Issues 49 Pull Requests Actions Packages Projects Wiki Activity

user-role-cluster (#760)
All checks were successful
CI/CD Pipeline / test (push) Successful in 11m2s
Details
CI/CD Pipeline / deploy-staging (push) Successful in 8m0s
Details
CI/CD Pipeline / deploy-main (push) Has been skipped
Details

Browse Source 
Reviewed-on: #760
This commit is contained in:
philipp
2024-10-11 11:20:58 +02:00
parent aca4fc82e4
commit bdde326f03
10 changed files with 199 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/db/README.md
View File

@ -9,6 +9,7 @@ Thus, here is the current (October '24) model and the reasoning behind it:
- All user-relevant fields are stored in `User`.
- `Role` (and its associative table `UserRole`) map current roles the user has. This is used for e.g. permissions (`Vorstand`, `Admin`, `cox`, ... roles) and fee calculation (`Donau Linz`, `scheckbuch`, `Rennjugend`).
- `Family` specifies, well, a family. Currently only used for fee calculation.
- `cluster` in `Role` groups roles together. There is a db check to only allow for at most 1 role of the same cluster (e.g. either `cox` or `bootsfuehrer`, but not both).
## Planned rowing adventures :-)
![](./planned.svg)