So you’ve seen LINQ to SQL in action and it looks like voodoo. How does the compiler turn that funny looking query statement that you’ve written in C# and make a working SQL query out of it? There are a couple of other key parts to it, but right in the middle are expression trees, forming the neutral map from which either a lambda statement (which is what your LINQ query breaks up into) or a SQL query can be generated. Continue reading
LINQ to SQL is designed to be a rapid application development tool for smaller applications. With this in mind, you probably wouldn’t expect it to scale particularly well – but this doesn’t mean that you shouldn’t be concerned about how it handles your connections under the hood! Continue reading
On one of the Readify mail lists there was a question raised about whether LINQ to SQL would support LINQ to Oracle. There was some discussion over if a direct use would work, passing an Oracle friendly connection object to the data context (which accepts an IConnection) or if a 3rd party option was available. I went away for a day or two down to the coast and returned to see another email in the chain pointing out something we hadn’t thought of…
Why use LINQ to SQL at all? Why not use LINQ to Entities! The email also linked to a post that has a nice concise summary of when you should use LINQ to SQL and when LINQ to Entities is appropriate. The blog post is available here, and I recommend that you continue on through to the linked MSDN article for more info (which is available here for quick reference).
Thanks to Chris for the idea and the pointer to this article!