Daniel Rall wrote:
> > IMHO using the login name as foreign key is bad database design. Two
> > reasons:
> >
> > 1. The login name of an user might change on some systems.
> >
> > 2. It will also cause your database to be a lot larger(and therefore
> > slower).
>
> I agree with Gunnar's objections to the use of login name as primary
> key--auto increments should always be preferred over text strings.
I agree with the above, but how should we handle the situation where
the user data is stored in LADP, and there is *no* numerical id?
The only idea I have right now is to have the LDAPUserManager
maintain a fake table id the DB that holds name <-> ID Mapping.
Not very clean (Our system uses this apprach at te momement).
Using the login name as the key would handle that. Moreover,
if you have an index created for the textual column, selects
will suffer very little performance penalty.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
