Re: XML Database schema for DatabasePsmlManager Implementation

[Atul Dambalkar]

>
>Why not? Don't you want to simply extend Turbine's User/ACL system instead
>of inventing your own?

I guess, I was trying to extend Turbine's schema..by using a foreign-key 
reference..

And as I said in one of previous emails, extending Turbine schema doesn't 
make sense in case of File System/LDAP Psml manager service implementations..

> > I have created new schema, please review it. I am a bit, skeptical about
> > it's correctness, in using TURBINE_USER.USER_ID as foreign key... For the
>
> >
> >    <index name="JETSPEED_ROLE_PROFILE_INDEX">
> >      <index-column name="ROLE_NAME" />
> >      <index-column name="MEDIA_TYPE" />
> >      <index-column name="LANGUAGE" />
> >      <index-column name="COUNTRY" />
> >      <index-column name="PAGE" />
> >    </index>
> >
> >  </table>
>
>What is the point of this table and its columns?

The point of all the above tables and columns is to define a unique key 
combination to identify a PSML profile and put it in database.

>Do you understand what a Group and what a Role/Permission is?

I am not at all interfering with that..  I guess, all that happens in 
ProfilerService rather than PsmlManagerService, even before 
PsmlManagerService gets invoked...This is just a parallel DB implementation 
of PsmlManagerService to CastorPsmlManagerService.

I guess, we are complicating things..

-Atul



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]