The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Privilages:
id
Sitemap_id
Groups_id #id of some user group
#privilages

Then I was wondering, I have many classes that can be loaded from the sitemap (eg Chat, News, Gallery etc..)and they all use different type of privilages, should I put privilages for each Class in its own table? or should a put all privilages for all classes in the Privilages table?

Still all classes have some privilages the same eg 'view' but it really doesn't 'mean' the same thing for the classes. They also have a lot of different privilages (eg Gallery has 'addPicture', but not addNews etc...)

Which way should I go? Create a large table full of 'unused' columns or seperate it to many tables that would though only have one line for each group that matches 1 sitemap line?

If this is not good explenation I urge you to reply and tell me so and I'll add further details!!!