Database Authentication
From: Alphonse Giambrone (NOSPAMa-giam_at_example.invalid)
Date: 09/20/04
- Next message: Jason: "Re: What is the best way to handle old browser versions?"
- Previous message: Steven Spits: "Re: About the Tabstrip and Multipage. Urgent !!!"
- Next in thread: GrantMagic: "Re: Database Authentication"
- Reply: GrantMagic: "Re: Database Authentication"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 20 Sep 2004 10:08:28 -0400
I have seen many sample of code authenticating a user by querying a
database.
Some lookup against only the login and return the password which is then
compared to the user entered password in the application code. Something
like:
Select password from users where login = 'userlogin'
if password = enteredpassword then
userisauthenticated.
end if
Others lookup against both. Something like:
Select UserID from users where login = 'userlogin' and password =
'enterpassword'
if not userid is null then
userisauthenticated
end if
I would like to know the advantages/disadvantages of the two methods.
Possibly that some databases can't apply case sensitivity to a where clause
or something else?
TIA
-- Alphonse Giambrone Email: a-giam at customdatasolutions dot us
- Next message: Jason: "Re: What is the best way to handle old browser versions?"
- Previous message: Steven Spits: "Re: About the Tabstrip and Multipage. Urgent !!!"
- Next in thread: GrantMagic: "Re: Database Authentication"
- Reply: GrantMagic: "Re: Database Authentication"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|