title: Best Practice / Standard for storing an Address in a SQL Database
body: <p>I am wondering if there is some sort of "standard" for storing US addresses in a database? It seems this is a common task, and there should be some sort of a standard. </p>
  
  <p>What I am looking for is a <strong>specific</strong> schema of how the database tables should work and interact, already in third normal form, including data types (MySQL). A good UML document would work. </p>
  
  <p>Maybe I'm just being lazy, but this is a very common task, and I am sure someone has published an efficient way to do this somewhere. I just don't know where to look and Google isn't helping. Please point me to the resource. Thanks.</p>
  
  <p>EDIT</p>
  
  <hr>
  
  <p>Although this is more of a general question, I would like to clarify my specific needs.</p>
  
  <p>Addresses will be used to specify road addresses of locations of events. These addresses will need to be in a format that can be best broken down and searched, and also used by any third-party applications I may end up linking my data source to.</p>
  
  <p>ALSO. Data will be geo-coded (long, lat) on entry and stored separately, so it must fit the (yet undecided) protocol of whatever geocoder / application / library does that. </p>