This is Sébastien Lorion's TypePad Profile.
Join TypePad and start following Sébastien Lorion's activity
Sébastien Lorion
Recent Activity
Hum, I guess I should have previewed my comment ...
Func<Northwinds, IQueryable<Orders>, int> q = CompiledQuery.Compile(
(nw, orderid) =>
from o in nw.Orders
where o.OrderId == orderid
select o);
Commented Mar 19, 2010 on Compiled or Bust? at Coding Horror
Compiled or Bust?
While I may have mixed emotions toward LINQ to SQL, we've had great success with it on Stack Overflow. That's why I was surprised to read the following: If you are building an ASP.NET web application that's going to get thousands of hits per hour, the execution overhead of Linq queries is goi...
Or if it's a class field declaration:
Func, int> q = CompiledQuery.Compile(
(nw, orderid) =>
from o in nw.Orders
where o.OrderId == orderid
select o);
Commented Mar 19, 2010 on Compiled or Bust? at Coding Horror
Compiled or Bust?
While I may have mixed emotions toward LINQ to SQL, we've had great success with it on Stack Overflow. That's why I was surprised to read the following: If you are building an ASP.NET web application that's going to get thousands of hits per hour, the execution overhead of Linq queries is goi...
You are putting the compiled query syntax in a bad light.. It would be a better example if you take advantage of type inference:
var q = CompiledQuery.Compile(
(Northwinds nw, int orderid) =>
from o in nw.Orders
where o.OrderId == orderid
select o);
Commented Mar 19, 2010 on Compiled or Bust? at Coding Horror
Compiled or Bust?
While I may have mixed emotions toward LINQ to SQL, we've had great success with it on Stack Overflow. That's why I was surprised to read the following: If you are building an ASP.NET web application that's going to get thousands of hits per hour, the execution overhead of Linq queries is goi...
Sébastien Lorion is now following The Typepad Team
Mar 19, 2010
Subscribe to Sébastien Lorion’s Recent Activity
