title: RavenDB document structure vs relational schema
body: <p>I have recently started to work with RavenDB.</p>
  
  <p>Here's a traditional example in relational db:</p>
  
  <h2>EmployeeType</h2>
  
  <p>ID:1 TYPE:DEV
  ID:2 TYPE:QA</p>
  
  <h2>Employee</h2>
  
  <p>NAME:FRED TYPEID:1<br/>
  NAME:JACK TYPEID:2<br/></p>
  
  <p>From what I understand of RavenDB the type would be included with the employee:</p>
  
  <h2>Employee</h2>
  
  <p>NAME:FRED TYPE:DEV<br/>
  NAME:JACK TYPE:QA<br/></p>
  
  <p>Would there then be a need for the EmployeeType table?</p>
  
  <p>If not, if you were to display a drop down list of employee type, would you just select distinct(Type) from Employee?</p>
  
  <p>If you were to do the above, how would you add a new employee type, without entering a new employee (or editing an existing one)? Or would you just keep a list in code somewhere?</p>
  
  <p>And lastly, if the text for an employee type were changed, it seems like you would then need to update all the employee records. What if there are 100,000 employee records?</p>
  
  <p>I'm new to Raven (document databases), so any insight to help me better grasp the different paradigm would be appreciated.</p>