on 1/10/2001 5:45 AM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
> The reason for that is, that numerical USER_ID is specific to database
> implementation of SecurityService/UserManager. In LDAP for example,
> there are no such ids.
>
> Applications that wish to be compatible with all Turbine configurations
> they may be deployed in, should *not* depend on those numerical ids.
> Use LOGIN_NAMEs instead. They are guaranteed to be unique.
>
> Applications that don't care about being compatible shoud cast User to
> BaseObject (TurbineUser extends it) and use getIdAsInt() or
> getPrimaryKey()
> or whatever it is called now, to get the id.
>
> Rafal
Rafal, the problem with this is that if you are using a relational database
in the background, you *will* need to get access to that ID in order to do
relationships with other tables. For example, relating a user to a project
or an issue_id. Therefore, I think it is an ugly hack to have to cast to a
TurbineUser object in order to simply get this ID.
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
