Timeline for Storing menu items with user permissions
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2013 at 14:08 | history | edited | Reactgular | CC BY-SA 3.0 |
deleted 5 characters in body
|
| Jul 29, 2013 at 14:06 | comment | added | span | Awesome answer. I will keep this in mind next time I do something likt this. For now I think user61852 solution will suit best since it doesn't require as many changes to the existing code. Thanks! | |
| Jul 29, 2013 at 14:01 | comment | added | Ed James | @MatthewFoscarini No worries, I'm not really bothered as long as a codebase is consistent ;) | |
| Jul 29, 2013 at 14:01 | history | edited | Reactgular | CC BY-SA 3.0 |
added 431 characters in body
|
| Jul 29, 2013 at 13:56 | comment | added | Reactgular | @EdWoodcock oh very good point. I should have gone with a permission level (int) and then compared that to the user's group level. I'll change that. Note, plural names habit caused by my use of CakePHP. Which is strange, cause the framework uses singular aliases for tables in queries. | |
| Jul 29, 2013 at 13:52 | comment | added | Ed James | This design would only allow each MenuItem to be tied to a single UserGroup, meaning either limited menus or data duplication. In reality you want a link table, ideally. Also, your choice of DB table naming as plurals makes me sad ;) | |
| Jul 29, 2013 at 13:49 | history | answered | Reactgular | CC BY-SA 3.0 |