title: How would I organize a Postgres db for a list of restaurants and their menu items?
body: <p>I'm playing around with Postgres and trying to get the hang of more complex issues. Imagine I have a large set of restaurants in each of the 50 U.S. states. Each restaurant contains a menu, and each menu contains a set of items which contain things like price, description, etc. What would be a good way to organize the data? </p>
  
  <p>My initial thought, which I'm sure is way wrong, would be to have a db per state. Within that would be a list of restaurants (and any basic details like address, phone number, rating, etc). Then, I'd have one db per restaurant which represents the menu. This db would contain columns that define each menu entry.</p>
  
  <p>Is this totally off the mark? Is there a more ideal way to accomplish this? My current experience playing around with Postgres has just been limited to a single database. </p>
  
  <p>I'm just looking for a good description, not a bunch of code. This is more a general architectural question. Thanks in advance!</p>