title: SQLite DB design for Android App
body: <p>I am building a database for an Android app using SQLite. The database consists of Zip code long/lat information. At runtime, a row will be added to a table in the database. I am trying to find the best way to design the database for both scalability and speed. This app will be released for all US states.</p>
  
  <p>My question is this:
   Would it be better to create a table for each US zip code, which stores this new information (and query the DB at runtime)</p>
  
  <p>Or, would it be better to create 1 table in which all new data is added (and query the DB at runtime)?</p>
  
  <p>-I might have answered my own question here, but the data added will only be kept in the database for approx. 1 week (most likely only a few days).</p>
  
  <p>Any advice would be great! </p>