on 9/7/01 1:22 PM, "David Sean Taylor" <[EMAIL PROTECTED]> wrote:
> Its a one-to-many relationship. One user can have multiple profiles.
> I believe that we don't want to extend the TURBINE_USER table, we need to
> create a new table JETSPEED_USER_PROFILE,
> which is related to the TURBINE_USER table on the primary key of
> TURBINE_USER.
Correct.
> Perhaps there is another way to do this in Torque?
Of course there is a way to do that in Torque.
> Looking at the link above, I believe Atul has the foreign key declarations
> correct.
> How is this done differently in Scarab?
Look at it. If you are going to extend the TURBINE_USER table, then there is
more work that needs to be done in the XML file to define things.
> to store profiles for roles
I don't think that is a good idea. Roles are associated with Users and Users
are associated with Profiles. If you want to know all of the profiles for a
given role, you should look at your Users to get that information.
> To store profiles for groups.
You do realize that a "group" is not a group of users, but is really a
Project. It is badly named in Turbine (we have a proposal to fix it), but
group == project.
>> Do you understand what a Group and what a Role/Permission is?
>
> We have the concept of groups in Jetspeed, and we are using the TURBINE_GROU
> P table to store the groups.
> In the Turbine model, there is the USER_GROUP_ROLE table which holds the
> relationship that a user is in a group under a given role.
NOOOOOOOOOOOO!!!!!!!!!! That is not correct.
A User is in a Project under a given role. It isn't a group of users it is
users in a project.
> Permissions are defined on a per role basic, defined in the
> TURBINE_ROLE_PERMISSION table.
> I haven't checked recently, but Ive heard that the GROUP table will be
> renamed in the next version of Turbine.
Correct.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
