Repository pattern and return types

Question

I am using the repository pattern where I have one repository class per database table. I was wondering how you guys approach queries that only need to return a specific number of columns

For example say I have the following

Item Table (fictional table)

ItemId
Name
PurchaseDate
Description
Price

In my code I create an object with the fields above called Item.cs (currently not using an orm).

If I have multiple scenarios where I need to return

1. ItemId
2. A combination of PurchaseDate and Name
3. ItemId and price

Which would be the best approach?

1. Get all fields from the items table and return an Item object (1 repo query)
2. Create three queries in Repo and return an Item object for each one
3. Create three queries in Repo and return only what is needed?

Now imagine this scenario with a table with over 10 fields.

Personally, I like option one, but I'm not sure if there is a better way to go about this.

Answer 1

I add methods to my repositories when I need them in contrast to generic repositories where you get a set of methods no matter if you need them or not.

Returning IQueryable is a leaky abstraction.

Take a look at Domain Driven Design (the book) and you'll get a good idea of how well designed repositories should look like.

I've also written a rant about generic repositories: http://blog.gauffin.org/2012/02/generic-repositories-a-silly-abstraction-layer/