title: How to store site wide settings in a database?
body: <p>I'm debating three different approaches to to storing sitewide settings for a web application.</p>
  
  <p>A key/value pair lookup table, each key represents a setting.</p>
  
  <ul>
  <li><b>Pros</b> Simple to implement</li>
  
  <li><b>Cons</b> No Constraints on the individual settings</li>
  </ul>
  
  <p>A single row settings table.</p>
  
  <ul>
  <li><b>Pros</b> Per setting defaults and constraints</li>
  <li><b>Cons</b> - Lots of settings would mean lots of columns. Not sure if Postgres would have an issue with that</li>
  </ul>
  
  <p>Just hard code it since the settings won't change that often.</p>
  
  <ul>
  <li><b>Pros</b> Easy to setup and add more settings.</li>
  <li><b>Cons</b> Much harder to change</li>
  </ul>
  
  <p>Thoughts on which way to go?</p>