Database Design
First off. Thank you to everyone that has posted comments/suggestions.
I have been looking over the suggestions for the database design… and I had started to modify the design to reduce the number of tables, but in the end I feel that the tables should stay as normalized as possible.
A table should hold data specific to a certain “grouping” of data, be it member, group, module or theme.
This weekend I hope have the design finalized (fingers crossed).
January 5th, 2008 at 6:08 am
Really interesting, pressed to see next release !! héhé !
Cool to reduce nombers of table… for easy implementation in existing apps/
thx
January 5th, 2008 at 12:02 pm
Looking forward to see your finalized solution.
Using a normalized table approach usually results in one additional table to handle one-to-many relationships (i.e. a user being a member of multiple groups), but the approach is extensible in the future if someone needs a finer-grained authorization solution. Case in point, the following link shows a fine-grained RBAC solution based on the use of normalized tables while following NIST guidelines. You can see how the approach could be applied to your original design to add fine-grained authorization all the way down to a module’s content item level.
http://www.sqlrecipes.com/database_design/fine_grained_role_based_access_control_rbac_system-3/
January 5th, 2008 at 12:59 pm
Thanks for the link mmx. I’ll check it out.