One repository per table or one per functional section?
Posted
by Ian Roke
on Stack Overflow
See other posts from Stack Overflow
or by Ian Roke
Published on 2010-06-06T14:42:53Z
Indexed on
2010/06/06
14:52 UTC
Read the original article
Hit count: 375
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.
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?
Which is the best practise for this type of work? I am still new to this method of coding.
© Stack Overflow or respective owner