Timeline for Design an extensible permissions model in database
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2022 at 11:20 | comment | added | Flater | (1) You're talking about "only new permissions" when a product "changes"; which implies that permissions get revoked when on product update. How else are you going to distinguish permissions that were given before/after said update to the product? (2) Just because you're using an OOP language does not mean that the OOP tag is relevant - the question is whether the question you're asking is rooted in OOP, which for your case it isn't. (3) If you need to be able to set a user's permissions without the need of having a product; how will you define to which products the permissions apply? | |
| Apr 1, 2022 at 18:32 | answer | added | Nachokhan | timeline score: 3 | |
| Jan 15, 2021 at 16:58 | comment | added | Fausto Sanchez | The revoke is not necessary. When the product change, only new users should get the new permissions | |
| Jan 15, 2021 at 14:12 | comment | added | Greg Burghardt | If the permissions associated with a product change, do you want all permissions for user who purchased that product to reflect that change? | |
| Jan 15, 2021 at 14:11 | comment | added | Greg Burghardt | Would you ever need to revoke a permission that was given to the user from a purchase? | |
| Jan 15, 2021 at 14:06 | comment | added | Greg Burghardt | @RobertBräutigam: if an object oriented language is using a relational database, then both apply. The challenge is adapting the object oriented model to the relational database. I think tackling both in one question is too broad. Focus on database first, then the OO model. | |
| Jan 15, 2021 at 12:57 | history | edited | Fausto Sanchez | Remove unrelated tags | |
| Jan 15, 2021 at 9:23 | comment | added | Robert Bräutigam | You are conflating database design with software design. If you are looking for a proper relational database schema, this has nothing to do with code. If you are looking for a model in code, that has nothing to do with the database. The question seems to be about the database, so remove at least the "object-oriented-design" tag. | |
| Jan 15, 2021 at 1:28 | comment | added | Fausto Sanchez | I wrote that option but saying that this is not possible because the permissions should be also manageable per user without the need of having a product | |
| Jan 14, 2021 at 23:44 | comment | added | Greg Burghardt | A user buys many products. A product has many permissions. A user has many permissions through the products they buy. | |
| Jan 14, 2021 at 20:54 | history | asked | Fausto Sanchez | CC BY-SA 4.0 |