Should i create separate login table??

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • silwar
    New Member
    • Mar 2011
    • 7

    Should i create separate login table??

    Qusetion 1

    I am developing a website mainly for maintaining students record in asp.net and using sql server 2005 database as backend.

    These site has three types of user Admin, faculty and student.

    Each user have some similar info (user id, password, email, contactno, status) and some different info to be stored(e.g. department, class, section, etc).

    All will login to website.

    I have three different tables containing personal information for each type of user namely admin, faculty & student

    Question is

    whether to store login information in these tables with personal info(separate for each user)

    or

    create a new table only for login purpose and maintain personal info in different table. and map user id in login table as foreign key from personal info table

    NOTE:
    At the time of login user selects which type of user he is using radio button.


    Which is the better approach please suggest. I am confused. throw some light.


    *************** *************** *************** ***********


    Question 2

    If I create separate login table how will I map user ID from 3 different personal info table to login table as foreign key where they again act as primary key?

    (userID will be Primary key in personal info table in each table)
    Last edited by silwar; Apr 14 '11, 05:19 PM. Reason: Editing information provided to make it more understandable
Working...