Before you start dealing with SQL and tables, consider using a framework like Symfony instead. That way, you can integrate security, logging in and all the other tricky stuff from the start.
Cheers Jevon On Thu, Jul 22, 2010 at 6:59 PM, Rimu Atkinson <[email protected]>wrote: > 'family' table > family_id > name > > 'users' table: > user_id > family_id > first name > last name > login > password > etc > > > 'page' table: > page_id > title > body > creator_id > > 'page_editors' table: > user_id > page_id > > The page editors table keeps track of who can edit which pages. Existing > editors can choose other family members to grant access to. Maybe only allow > deletion of pages by the original creator of the page (creator_id). > > > On 22/07/10 16:28, Anthony Power wrote: > > Just starting on a new PHP project and need some advice on best method > to set-up database.... > > The project will be a family tree where members of my family will have > there own custom status page with photo and some text & member of > family be able to edit there own status page but maybe one member of > family can edit 3 status pages? > > Now back to database what best way set-up so can lock down users to > only be able edit pages that admin give them rights too & by giving > admins overall rights to edit and status page? > > Just need some advice on best way about doing this. > > Thanks , > Anthony Power > > > > > -- > Phone (04) 381 4827 or 021 823 129 > Skype rimu123 > Web http://rimu.geek.nz/ > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected]<nzphpug%[email protected]> > -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
