From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Dinesh Visweswaraiah <dinesh(at)trailblazingsolutions(dot)com> |
Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: SQL Intersect like problem |
Date: | 2003-02-06 16:33:14 |
Message-ID: | 20030206163314.GA21780@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Thu, Feb 06, 2003 at 10:17:15 -0500,
Dinesh Visweswaraiah <dinesh(at)trailblazingsolutions(dot)com> wrote:
> Hi Oliver,
>
> Actually the story is a little different. I used Invoice and Product
> and Quantity because everybody understands those. Reality is that
> this is a table that has AuthorizationSetId, UserId and Privileges.
> Objects in my application have a set of authorizations with specified
> userid and privileges, specifying who is permitted to do what. The
> Idea is to identify a AuthorizationSetId so that when the set of
> UserId and Privileges change, I can reuse a AuthorizationSetId rather
> than create a new one. In fact without reuse, there is no point
> in having a AuthorizationSetId in the first place.
If you are trying to group commonly associated security rights to simplify
administration, then the normal way to do this is with roles.
You have a table relating users and roles and another table relating
roles and security rights. By joining these two tables you get the
security rights for an individual user.
From | Date | Subject | |
---|---|---|---|
Next Message | Jennifer Lee | 2003-02-06 16:40:14 | using copy to insert data. |
Previous Message | Molenda, Mark P | 2003-02-06 16:30:18 | Html output |