locked
Career Page DB design RRS feed

  • Question

  • User-2123122692 posted

    I’m trying to build a career page from scratch and I need some help designing my database:

     

    Here is what I have so far. Any ideas how to design it correctly? All candidates will have to create a profile before viewing jobs.

     

    Candidates

    ID

    FirstName

    LastName

    Address

    City

    State

    Zip

    Email

    Tel

    Job Interest

    Resume (file name of resume like resume.doc)

     

    Job

    ID

    JobTitle

    JobLocation

    DatePosted

    JobDescription ( file name of job description like WebDeveloper.doc)

     

    Login

    ID

    UserName

    Password

    FirstName

    LastName

    Active

    Level

     

    Applied

    ID

    FirstName

    LastName

    JobID

    JobTitle

    DateApplied

     

     

    Friday, June 3, 2011 3:29 PM

Answers

  • User1867929564 posted

    Wht are the use of login table.
    If it has some other use other than validate User .Then you can keep sperate login table elase it is not require.

    In Candidate Table you can hv,
    previous thing and

    UserName (Unique)

    Password

    Active

    Level

     

    Applied

    JobID

    JobTitle

    DateApplied
    UserName  

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, June 6, 2011 5:52 AM

All replies

  • User1446927574 posted

    Why dont you Use ASP.NET Membership and Profiles to store user information.

    Friday, June 3, 2011 3:39 PM
  • User3866881 posted

    Hello:)

    You have many duplicated fields. In fact you can try this to simplify——

    Users(For both login and finding jobs)

    1) Id (primary key)

    2)First Name

    3)Last Name

    Jobs(For listing jobs for choosing)

    1) Id (primary key)

    2)JobName

    ………………

    Users_Jobs

    1) Id (primary key)

    2) JobId (foreign key to Jobs)

    3) UserId(foreign key to Users)

    Saturday, June 4, 2011 10:52 PM
  • User1867929564 posted

    Wht are the use of login table.
    If it has some other use other than validate User .Then you can keep sperate login table elase it is not require.

    In Candidate Table you can hv,
    previous thing and

    UserName (Unique)

    Password

    Active

    Level

     

    Applied

    JobID

    JobTitle

    DateApplied
    UserName  

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, June 6, 2011 5:52 AM