+1  A: 

No. Repositories should represent domain model concepts, not entity level concepts, and certainly not database level. Think about all the things you would want to do with a given component of your domain, for example, Spaces.

One of the things that you'll want to do, is GetSpaceCategories(). This should definitely be included in the Spaces repository, as anyone dealing with Spaces will want access to the Space categories without having to instantiate some other repository.

A generic repository would be fairly counter-productive I would think. Treating a repository like a utility class would virtually guarantee that any moderately complex operation would have to instantiate both repositories.

womp  2009-07-22 22:04:49
With this approach, UpdateSpaceCategory(SpaceCategory spaceCategory) and DeleteSpaceCategory(string id) would also be in the ISpaceRepository as well, correct?
Ryan Taylor  2009-07-22 22:53:21
For sure. The purpose of the repository is to hide the underlying data access. If you were to switch out your database layer, the rest of your program would still be calling GetCategories() or UpdateCategory() on the repository - the change would be transparent to the repository consumer.
womp  2009-07-22 23:44:42

related questions

Transactions in the Repository Pattern
Repository Pattern and Item Deletion when using SQL Backend
IRepository confusion on objects returned
Linq to Sql and the Repository Pattern.
Repository Pattern: how to Lazy Load? or, Should I split this Aggregate?
Blog Architecture Design, using MVC and DDD
Does this Entity Repository Service example fit into Domain-Driven Design?
What is wrong with putting Using Blocks in Repository?
MVC: Repositories and Services
Decorator Chaining of Repositories and Specialized Repositories with Dependancy Injection
MVC Repository Pattern: Creating Model Classes
How many types should be implementing the Repository pattern?
How do you mock your repositories?
Repository Pattern and layering. Where do I apply security?
How should I structure a simple ASP.NET MVC app?
.net architecture: Creating a IRepository<T> generically
Entity Framework, building query based on criteria
Service Layers and Repositories
DDD repositories as singletons?
Constructing a Domain Object from multiple DTOs
Entity classes decoupled from LINQ to SQL provider for implementing the Repository pattern. How?
Which object should I mock?
Implementation example for Repository pattern with Linq to Sql and C#
Repository Pattern Implementation Experience
Repository pattern tutorial in C#