|
|
Posted by Sanders Kaufman on 09/29/07 18:26
"klenwell" <klenwell@gmail.com> wrote in message
news:1191040960.993523.31210@w3g2000hsg.googlegroups.com...
> On Sep 28, 5:39 pm, "Sanders Kaufman" <bu...@kaufman.net> wrote:
>> I try not to make it any bigger than userid and password - putting all
>> that
>> other stuff into linked tables.
>> That way, later, if you cange the other stuff, you don't have to mess
>> with
>> the actual login table.
>
> Interesting approach. What parts of a user's account or identity
> would you consider fixed or essential?
Like I said - userid and password.
> I always thought of a user's email as the binding factor as that's
> usually how significant account changes get validated. And I assumed
> that either the email address or the user name would have to remain
> fixed to maintain a continuous record.
Yeah, in a lot of systems, the email address is the user_id.
But if it's not, then atomicity says it should be in some other table.
Navigation:
[Reply to this message]
|