title: How shoud be a parameters table designed and used on businesses and GUI layers?
body: <p>I'm currently designing an application and I need to know how should be designed a constants parameter table. Also, I want to know how to use this table on the application. </p>
  
  <p>For example: for a parameter sex (M or F) in a system, it should be in its own table or is better to have that parameter with others in a special table?. How can I "envelope" parameters in the subsequent layers (using a constants class with the parameters and their primary keys)?</p>
  
  <p>I have heard about a special "DB pattern" or a common way to create a table such that its schema lets the development process to relay on this single parameter table. Do you know how's this called?  </p>
  
  <p>Also... could you recommend me any good bibliography on the issue?</p>