2. PHPRunner General questions
  3. [SOLVED]  Database Design Question
This topic is locked
[SOLVED]

 Database Design Question

 		4/15/2010 2:37:48 PM
PHPRunner General questions
P
 procheck author

I'm creating an office pool website and each pool (1 to many pools) will have a separate administrator. I'm not sure whether to create a separate user table for each pool or create one user table for all pools. The security in PHP runner works in such a way that I would need to add code to make sure that the admin can only view/change his own pool using a poolid if I use one table.
From a performance and design perspective, how feasible is it to create a table for every pool?

The user table could be very small from 5-10 up to 200+. It would be much easier to create separate user tables, but is this a good idea from a design perspective since I am basically holding the same data in each.
Thanks
Al
Sergey Kornilov admin 4/15/2010

You absolutely should not create a separate user table for each pool.
Add PoolId field to users table and enable advanced security mode 'Users can see all data, can edit their own data only'. Use PoolID from users and from the main table to link data. This is it.
P
 		procheck author 4/16/2010



You absolutely should not create a separate user table for each pool.
Add PoolId field to users table and enable advanced security mode 'Users can see all data, can edit their own data only'. Use PoolID from users and from the main table to link data. This is it.


I got it working. I had only setup the user table and not the other tables. I also had the Admin Group checked. I

didn't really know what this was doing but I now see it's purpose.
Thank-you!