title: One repository per table or one per functional section?
body: <p>I am using ASP.NET MVC 2 and C# with Entity Framework 4.0 to code against a normalised SQL Server database. A part of my database structure contains a table of entries with foreign keys relating to sub-tables containing drivers, cars, engines, chassis etc.</p>
  
  <p>I am following the Nerd Dinner tutorial which sets up a repository for dinners which is fair enough. Do I do one for drivers, one for engines, one for cars and so on or do I do one big one for entries?</p>
  
  <p>Which is the best practise for this type of work? I am still new to this method of coding.</p>