I am building a document database for the storing and controlling of documents.
My current thinking is to have a object table, where everything that is created has a unique ID, this would apply to users, documents, projects etc. The unique id would be database wide, and different from say a user id.
Then my plan is to create a master ACL table with columns object_id , user_id , permission1 , permission 2 etc.
This way one could change the permissions of the 'object' regardless of whether it's a document, folder, project, user group etc.
The main problem as I see it, is the master ACL table would have number_of_users*number_of_objects rows. Assuming that we generate a few 1000 objects in the lifetime of the database, and we have upto 300 people using it, this means about a few 100 thousand rows, is this big or not?
Is there a better way to do it?
Cheers
Paul
My current thinking is to have a object table, where everything that is created has a unique ID, this would apply to users, documents, projects etc. The unique id would be database wide, and different from say a user id.
Then my plan is to create a master ACL table with columns object_id , user_id , permission1 , permission 2 etc.
This way one could change the permissions of the 'object' regardless of whether it's a document, folder, project, user group etc.
The main problem as I see it, is the master ACL table would have number_of_users*number_of_objects rows. Assuming that we generate a few 1000 objects in the lifetime of the database, and we have upto 300 people using it, this means about a few 100 thousand rows, is this big or not?
Is there a better way to do it?
Cheers
Paul