iqueryable

I am using NHibernate and Rhinomocks and having trouble testing what I want. I would like to test the following repository method without hitting the database (where _session is injected into the repository as ISession): public class Repository : IRepository { (... code snipped for brevity ...) public T FindBy<T>(Expression<Func<T, bool>> where) { return _session.Linq<T>().Where(where).FirstOrDefault(); } } My initial approach is to mock ISession, and return an IQueryable stub (hand coded) when Linq is called. I have a IList of Customer objects I would like to query in memeory to test my Linq

The answer to What is the expected performance of IEnumerable? says there's no way to know anyting about the performance of iterating an arbitrary IEnumerable. Each iteration could hit a database or make a web serivce call; or it might just return the next item in an array/list. Given that, is there a good way to indicate "this is fast"? For example, with T[] or List<T> instead of IEnumerable<T> I know that going from T[i] to T[i+1] will be quick. (Of course, forcing the enumeration to return a list/array could create other performance concerns. List<T> also exposes editable semantics.)

Building an application, before using a real database, just to get things work I can first use a hard-coded list as a fake, in-memory repository: public class FakeProductsRepository { private static IQueryable<Product> fakeProducts = new List<Product> { new Product{ ProductID = "xxx", Description = "xxx", Price = 1000}, new Product{ ProductID = "yyy", Description = "xxx", Price = 2000}, new Product{ ProductID = "zzz", Description = "xxx", Price = 3000} }.AsQueryable(); public IQueryable<Product> Products { get { return fakeProducts; } } } How to add a method to this class for adding new, not

I have a quite simple WCF service method which returns an IQueryable, just for testing. Perhaps I got something wrong when trying to understand what IQueryable is designed for. I clearly plan to use this with the IQueryable provider of NHibernate later. But first I ran into some sort of serialization problems (at least I think it might be the problem) whenever using a WCF method returning an IQueryable. It doesn't even work for a simple string. Here's my code: public IQueryable<string> GetEquipmentConfigurations() { var returnValue = new List<string>(); returnValue.Add("test"); return

Suppose I have an IQueryable<T> expression that I'd like to encapsulate the definition of, store it and reuse it or embed it in a larger query later. For example: IQueryable<Foo> myQuery = from foo in blah.Foos where foo.Bar == bar select foo; Now I believe that I can just keep that myQuery object around and use it like I described. But some things I'm not sure about: How best to parameterize it? Initially I've defined this in a method and then returned the IQueryable<T> as the result of the method. This way I can define blah and bar as method arguments and I guess it just creates a new

I have an interface that defines a repository from the Repository pattern: interface IRepository { List<Customer> GetAllCustomers(Expression<Func<Customer, bool>> expression); } I've implemented it against Entity Framework: class EntityFrameworkRepository { public List<Customer> GetAllCustomers(Expression<Func<Customer, bool>> expression) { return DBContext.Customers.Where(expression).ToList(); } } That seems to work well, it allows me to do something like: var customers = entityFrameworkRepository.Where( customer => String.IsNullOrEmpty(customer.PhoneNumber) ); Now I'd like to have an

Is there a way to know if an IQueryable<T> has been ordered (using OrderBy or OrderbyDescending )? So I know whether to call OrderBy or ThenBy on the collection. IQueryable<Contact> contacts = Database.GetContacts(); I tried contacts is IOrderedQueryable<Contact> , but it's always true. Edit : I just changed my example, the previous one wasn't really showing my point. Assume that GetContacts uses Entity Framework and simply returns all the records of a table. Later on, I apply several functions to contacts , I have no knowledge of what those functions do. They can sort or filter the IQueryable