title: Designing a database schema for a Job Listing website?
body: <p>For a school project I'm making a simple Job Listing website in ASP.NET MVC (we got to choose the framework). </p>
  
  <p>I've thought about it awhile and this is my initial schema:</p>
  
  <blockquote>
    <p><strong>JobPostings</strong><br>
    +---JobPostingID<br>
    +---UserID<br>
    +---Company<br>
    +---JobTitle<br>
    +---JobTypeID<br>
    +---JobLocationID<br>
    +---Description<br>
    +---HowToApply<br>
    +---CompanyURL<br>
    +---LogoURL  </p>
    
    <p><strong>JobLocations</strong><br>
    +---JobLocationID<br>
    +---City<br>
    +---State<br>
    +---Zip  </p>
    
    <p><strong>JobTypes</strong><br>
    +---JobTypeID<br>
    +---JobTypeName  </p>
  </blockquote>
  
  <p><em>Note: the UserID will be linked to a Member table generated by a MembershipProvider.</em></p>
  
  <p>Now, I am <em>extremely</em> new to relational databases and SQL so go lightly on me.  </p>
  
  <p>What about naming?  Should it be just "Description" under the JobPostings table, or should it be "JobDescription" (same with other columns in that main table).  Should it be "JobPostingID" or just "ID"?  </p>
  
  <p>General tips are appreciated as well.</p>
  
  <p>Edit: The JobTypes are fixed for our project, there will be 15 job categories.  I've made this a community wiki to encourage people to post.</p>