login table?

[Christos]

hi...

i have a table member and a table quest

i want to set usernames and passwords for the members and quests.

what is better?

to have a field called password and another field called username in both tables

OR

have a table called memberlog with fields memberid, password and username and another table called questlog with fields questid, password and username

if i do the second way then the relationship between member and memberlog will be 1:1 and mandatory for both sides therefore i must join the tables...isn't it?

Can anyone please tell me which way is better...?and why...?

Thanks in advance...

 

[Rob.Mills]

I'm not sure what you mean by quest. But I make a habit of creating a table to contain information about my users. One table is all I use. I put their id in it, password, and different fields to give the kind of permissions I want to set.

 

[Christos]

i am asking because i did it using the second way and i am afraid that is not correct...

thanks for the help...

 

[Christos]

yes but what is troubling me... are the relationships.

if i do it 1 table

Fields:

UserID
UserName
Password
UserType: Value would be either G (for guest) or M (for member)
Disabled: Y/N

what will be the relationship between the table member and the new table called e.g. login

i think it will be 1:1 but mandatory from both sides which is not right...

aaaaaa now i got it... the relationships may be mandatory but the table is not only related with one table but 2 tables(member and quest)...

thanks alot for the help. i got it... thanks

 

[Rob.Mills]

Oh!! You meant guest instead of quest. That makes a lot more sense.

Glad you got it figured out.