title: Database Architecture - dating site
body: <p>I am developing a dating website that will be based on lots of personal fields that users will choose from a list. I have 43 different fields that the user must fill - each field has multiple answer options. </p>
  
  <p>I have 3 options: </p>
  
  <ol>
  <li><p>to build all of the site hardcoded and set all the fields and their options in the code - that will be difficult to maintain.</p></li>
  <li><p>another option that I see now is to open a table for each field list and to fill it with its options.</p></li>
  <li><p>to open one table for each field list and to save its name and its id and another table for the field options wich will include fields id , and the name of the options.</p></li>
  </ol>
  
  <p>Those are the options I see - what will be the best way to go? Are there any other options I dont know of?</p>