Thanks Frank!
Just to be certain, cant I
If two users enter the same address
you will have two different records in the address table - identical
except
for the authority field.
store the information and just update the authority field? i.e If the are
two fields that look the same (made by
thanks for your answer! I already made the login page =).
/Ljungan
Adam Royle [EMAIL PROTECTED] skrev i meddelandet
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
I have done an address book in php, although I kept the
username/password in with the rest of their details. If you wanted to
keep
Im making an adressbook using PHP and mySQL.
I want each user to have access only to his/hers adressinputs. Now Im
wondering how I gonna solve this, ofcourse its very easy just to create a
table for each user but then the hole idea of database loose its purpose
=). How can I mark each input so
store and validate a username and password with each user's info
-Original Message-
From: Ljungan [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 22, 2002 11:07 AM
To: [EMAIL PROTECTED]
Subject: [PHP-DB] marking DB entries...
Im making an adressbook using PHP and mySQL.
I want each user
well...what the bloody hell are you looking for from us?
-Original Message-
From: Ljungan [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 22, 2002 11:29 AM
To: [EMAIL PROTECTED]
Subject: Re: [PHP-DB] marking DB entries...
well that wasn't very helpful... I have two tables already, users
I have done an address book in php, although I kept the
username/password in with the rest of their details. If you wanted to
keep it all in two tables, then go ahead. You really should have an ID
field in every table, whether you use it or not, and most of the times,
you'll find you will use
OK so you have 2 tables one for users login and one for the addresses a user
may store and retrieve.
Your users will login, you will validate their name and password combination
and have either a userID or the name is fine too (an integer ID is smaller
to store and possibly more efficient).
Now