http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Only works if you are referebcing the LuceneQuery through a IDocumentQuery. If you happen to have a reference to an IEnumerable which happens to be a LuceneQuery then the LINQ extension method will still get used. http://ayende.com/4655/disabling-linq#comment8http://ayende.com/4655/disabling-linq#comment8Tue, 12 Oct 2010 15:05:27 GMTOren, As Neil observed, there are many LINQ operators that can filter. Even Single() with no predicate is filtering, and as such will cause a full query to hit the DB, only to be filtered back into a single item. You should rethink this. If you do want to use linq-to-objects, you'll just have to add a single .AsObservable() method and then you could go run with your scissors. :-) http://ayende.com/4655/disabling-linq#comment7http://ayende.com/4655/disabling-linq#comment7Sun, 10 Oct 2010 21:13:26 GMTBut all the other methods mentioned take predicates to filter on, so it's the same thing. I would never write: .Where(x => x.Name == "ayende").FirstOrDefault(); But .FirstOrDefault(x => x.Name == "ayende"); There are so many extension methods, do you really want to Obsolete them all? Think I agree with Omer http://ayende.com/4655/disabling-linq#comment6http://ayende.com/4655/disabling-linq#comment6Sun, 10 Oct 2010 19:03:26 GMTA descriptive obsolescence as in NH. Maybe you should allow these queries to be executed from another interface, like ImProbablyMakingAMistakeSession or sth like this? http://ayende.com/4655/disabling-linq#comment5http://ayende.com/4655/disabling-linq#comment5Sun, 10 Oct 2010 19:01:27 GMTOmer, but that would mean that we couldn't do things like: First(), Single(), Count, etc http://ayende.com/4655/disabling-linq#comment4http://ayende.com/4655/disabling-linq#comment4Sun, 10 Oct 2010 18:42:51 GMTHow about stop deriving IDocumentQuery from IEnumerable, and adding an .AsEnumerable() method to it? This will make moving into the IEnumerable monad more explicit. http://ayende.com/4655/disabling-linq#comment3http://ayende.com/4655/disabling-linq#comment3Sun, 10 Oct 2010 18:37:24 GMTGood solution, not destroying the api but very clearly pointing the consumer in a better direction. http://ayende.com/4655/disabling-linq#comment2http://ayende.com/4655/disabling-linq#comment2Sun, 10 Oct 2010 14:23:13 GMTCreative. http://ayende.com/4655/disabling-linq#comment1http://ayende.com/4655/disabling-linq#comment1Sun, 10 Oct 2010 10:52:16 GMT