The Wayward WebLogOh, what a tangled webLINQ: Building an IQueryable Provider - Part VI- August 9, 2007 So, again you thought I was done with this series, that I've given up and moved on to greener pastures. You think that since Select works wonderfully that that's all you need to know to make your own IQueryable provider Ha! There's loads more to know. And, by the way, Select is still broken. ...(read more)http://blogs.msdn.com/mattwar/archive/2007/08/09/linq-building-an-iqueryable-provider-part... LINQ: Building an IQueryable Provider - Part V- August 3, 2007 Over the past four parts of this series I have constructed a working LINQ IQueryable provider that targets ADO and SQL and has so far been able to translate both Queryable.Where and Queryable.Select standard query operators. Yet, as big of an accomplishment that has been there are still a few gaping holes and Im not talking about other missing operators like OrderBy and Join. Im talking about huge conceptual gaffs that will bite anyone that strays from my oh-so-ideally crafted demo...http://blogs.msdn.com/mattwar/archive/2007/08/03/linq-building-an-iqueryable-provider-part... LINQ: Building an IQueryable Provider - Part IV- August 2, 2007 I just could not leave well enough alone. I had the crude LINQ provider working with just a translation of the Where method into SQL. I could execute the query and convert the results into my objects. But thats not good enough for me, and I know its not good enough for you. You probably want to see it all; the transformation of a little sample program into a full-fledged working ORM system. Well, Im probably not going to do that. However, I still think theres a lot of common ground I can...http://blogs.msdn.com/mattwar/archive/2007/08/02/linq-building-an-iqueryable-provider-part... LINQ: Building an IQueryable Provider - Part III- August 1, 2007 Part III Wasnt I done in the last post Didnt I have the provider actually working, translating, executing and returning a sequence of objects Sure, thats true, but only just so. The provider I built was really fragile. It only understood one major query operator and a few minor ones like comparison, etc. However, real providers are going to have to deal with many more operators and complicated interactions between them. For example, that provider did not even let you project the data into...http://blogs.msdn.com/mattwar/archive/2007/08/01/linq-building-an-iqueryable-provider-part... |