Comments on: Readability, Sub-Queries in LINQ

By: Steve

Steve — Fri, 28 May 2010 11:44:44 +0000

Me Like!

Thanks for the writeup. Linq2Sql is quite flexible. Didn’t think about doing it in the “select new{}” way. Good idea.

I was thinking about doing an “in” or “contains” style operator for seeing if a record contains information from another related table.. but this was good info to know.

By: Bruce

Bruce — Wed, 19 May 2010 20:35:09 +0000

Me Like!

Thanks for the writeup. Linq2Sql is quite flexible. Didn’t think about doing it in the “select new{}” way. Good idea.

I was thinking about doing an “in” or “contains” style operator for seeing if a record contains information from another related table.. but this was good info to know.

By: DaryFademem

DaryFademem — Sun, 01 Nov 2009 20:33:48 +0000

Other variant is possible also

By: Chad

Chad — Fri, 02 Oct 2009 03:40:13 +0000

I see the direction you’re going and I can’t argue that this may be more legible from a readability standpoint by breaking up the subquery as an IQueryable, then assigning the “var” to the Commission property in the actual select statement. My assumption (without validation of course) would be that you would end up with the exact same SQL output, which any optimizing tricks you can use when LINQ is generating your SQL and not you the better.

Of course, my idea of readability is putting everything humanly possible in a single statement (or single line if I can get away with it). I hate vertical space . This was a good suggestion though, thanks!

By: Frank

Frank — Thu, 01 Oct 2009 05:14:24 +0000

If you talk about readability i would split it up into 2 queries
var qcommision = from t in e.Orders
where t.ShippedDate.HasValue && t.ShippedDate (r.Quantity * r.UnitPrice) – Convert.ToDecimal(r.Discount)) * .1M).Sum(r => r)

and then

var employees = from e in northwind.Employees
select new
{
FirstName = e.FirstName,
LastName = e.LastName,
Title = e.Title,
Commission = qcommision
}

haven’t tested this but it think it would work this way also.

By: Travis

Travis — Tue, 04 Aug 2009 01:22:07 +0000

Me Like!

Thanks for the writeup. Linq2Sql is quite flexible. Didn’t think about doing it in the “select new{}” way. Good idea.

I was thinking about doing an “in” or “contains” style operator for seeing if a record contains information from another related table.. but this was good info to know.