Writing your own LINQ provider

Re:Writing your own LINQ provider by Guillaume86 on Monday March 17, 2014 @08:47AM (#7414690)

Nice post, if you plan a writing a full featured provider I recommend using the ReLINQ framework: http://relinq.codeplex.com/

I regret I didn't knew about it when I wrote my first LINQ provider.

[ Parent | on HN ]

Re:Writing your own LINQ provider by jdaley on Monday March 17, 2014 @09:08AM (#7414779)

Although it's quite a bit older than re-linq, I'll throw a recommendation in for IQToolkit: http://blogs.msdn.com/b/mattwar/archive/2008/11/18/linq-link...

I used it to build a LINQ provider for a legacy mainframe database system, abstracting away the incomprehensible table and column naming, weird date systems, EBCDIC, and other nastiness involved in querying that system using straight-up SQL.

One thing I found is that implementing a custom LINQ provider gives you a better understanding of how Entity Framework runs your queries. You get to see how queries get split up into the parts executed in the CLR versus the parts that get translated, and how expressions get rearranged and rewritten.

[ Parent | on HN ]

Re:Writing your own LINQ provider by aashishkoirala on Monday March 17, 2014 @10:38AM (#7415229)

I second the comment about getting a better understanding of how EF, etc. work after writing your own provider. Definitely.

[ Parent | on HN ]

Re:Writing your own LINQ provider by aashishkoirala on Monday March 17, 2014 @09:02AM (#7414752)

Thanks for the info - I just looked at the home page but have yet to try it out. Looks like it cuts down on a lot of the boilerplate associated with it. Nice.

[ Parent | on HN ]