August 2, 2010 at 10:45 pm
In my web application project i have packages, modules and documents (such as creatememo, createcircular,CreateEmployee). in my database i created tables for packages, associated modules and objects (employee, memo, circular). then i have action table that defines applicable actions on each object e.g create, List, edit, print etc. now i manage rights by a table that contain ids of users, objects and actions. semantically, each row of this table will be like user a can edit employee, user b can create employee etc. my question is if my approach appropriate. should i move to storing pages in database and managing rights on page level rather than on object level (currently followed)
August 3, 2010 at 11:56 am
tassadaque (8/2/2010)
In my web application project i have packages, modules and documents (such as creatememo, createcircular,CreateEmployee). in my database i created tables for packages, associated modules and objects (employee, memo, circular). then i have action table that defines applicable actions on each object e.g create, List, edit, print etc. now i manage rights by a table that contain ids of users, objects and actions. semantically, each row of this table will be like user a can edit employee, user b can create employee etc. my question is if my approach appropriate. should i move to storing pages in database and managing rights on page level rather than on object level (currently followed)
Assuming the words "object" and "page" are not used in their actual SQL Server meaning but in the particular meaning of this particular project... I don't know. What the business requirements say about it? 🙂
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply