Timeline for Role based Database Schema
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2017 at 16:07 | vote | accept | ss_millionaire | ||
| Jun 12, 2017 at 11:03 | comment | added | Glorfindel | @ss_millionaire either this or this (if you go for a separate Role entity). I don't have any ER software to show the foreign keys, but I hope it's clear. | |
| Jun 12, 2017 at 10:57 | comment | added | ss_millionaire | Please if it's not too much to ask, can you show me an ER diagram to illustrate this? I can't picture what you're saying. Thanks.. | |
| Jun 11, 2017 at 16:29 | comment | added | Glorfindel | This would only apply to Role-based access, and one DocumentPermission record would specify that (one) role X has access to (one) document Y. A document can have multiple DocumentPermission records. | |
| Jun 11, 2017 at 15:36 | comment | added | ss_millionaire | Thanks for the shrewd observation. For this point: "use the DocumentPermission entity to specify which roles have access to a certain Document (if the access type is role-based)", do you mean just adding a field like role_permission on the DocumentPermissions entity that specifies which role has access to the document based on the document id? And will this apply to all access types (Public, Private and Role based)? | |
| Jun 10, 2017 at 13:53 | history | edited | Glorfindel | CC BY-SA 3.0 | added 312 characters in body |
| Jun 10, 2017 at 13:45 | history | answered | Glorfindel | CC BY-SA 3.0 |