The RDBMS table needs to have some primary key to begin with, you just
need to put that primary key in LDAP. I don't see that as being
replication.
Where it's user id (my recommendation), or any other identifier is up to
you. And yes, if your table has a counter primary key you can put that
counter in LDAP (you can always add new attributes to your LDAP server).
arkin
> Thanks for the answer.
>
> This solution means replicating LDAP info in the RDBMS, if only the user id.
>
> Is this what people out there are doing? Or is it nobody is using
> LDAP with workflow apps etc ?
>
> Javier
>
> >Suppose the user information is stored in LDAP. Suppose the
> >rest of the application data is stored in an RDBMS.
> >
> >How can I make a query joining user and application data?
> >
> >Something like "select all jobs asigned to this user"
> >where job information is stored in RDBMS and user information
> >is stored in LDAP.
> >
> >Replicating all user data from LDAP into the RDBMS does not
> >look like a good solution.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
