StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1229863
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-08-04T20:51:05.470
FavoriteCount
0
LastActivityDate
2009-08-04T21:04:00.483
LastEditDate
2009-08-04T21:04:00.483
LastEditorUserId
22656
OwnerUserId
22656
ParentId
1229838
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
Do you mean in terms of a query expression, or what the query does behind the scenes? Query expressions are expanded into "normal" C# first. For example: <pre><code>var query = from x in source where x.Name == "Fred" select x.Age; </code></pre> is translated to: <pre><code>var query = source.Where(x => x.Name == "Fred") .Select(x => x.Age); </code></pre> The exact meaning of this depends on the type of <code>source</code> of course... in LINQ to Objects, it typically implements <code>IEnumerable<T></code> and the <code>Enumerable</code> extension methods come into play... but it could be a different set of extension methods. (LINQ to SQL would use the <code>Queryable</code> extension methods, for example.) Now, suppose we are using LINQ to Objects... after extension method expansion, the above code becomes: <pre><code>var query = Enumerable.Select(Enumerable.Where(source, x => x.Name == "Fred"), x => x.Age); </code></pre> Next the implementations of <code>Select</code> and <code>Where</code> become important. Leaving out error checking, they're something like this: <pre><code>public static IEnumerable<T> Where<T>(this IEnumerable<T> source, Func<T, bool> predicate) { foreach (T element in source) { if (predicate(element)) { yield return element; } } } public static IEnumerable<TResult> Select<TSource, TResult> (this IEnumerable<TSource> source, Func<TSource, TResult> selector) { foreach (TSource element in source) { yield return selector(element); } } </code></pre> Next there's the expansion of iterator blocks into state machines, which I won't go into here but which I have an <a href="http://csharpindepth.com/Articles/Chapter6/IteratorBlockImplementation.aspx" rel="nofollow noreferrer">article about</a>. Finally, there's the conversion of lambda expressions into extra methods + appropriate delegate instance creation (or expression trees, depending on the signatures of the methods called). So basically LINQ uses a lot of clever features of C#: <ul> <li>Lambda expression conversions (into delegate instances and expression trees)</li> <li>Extension methods</li> <li>Type inference for generic methods</li> <li>Iterator blocks</li> <li>Often anonymous types (for use in projections)</li> <li>Often implicit typing for local variables</li> <li>Query expression translation</li> </ul> However, the individual operations are quite simple - they don't perform indexing etc. Joins and groupings are done using hash tables, but straightforward queries like "where" are just linear. Don't forget that LINQ to Objects usually just treats the data as a forward-only readable sequence - it can't do things like a binary search. Normally I'd expect hand-written queries to be marginally faster than LINQ to Objects as there are fewer layers of abstraction, but they'll be less readable and the performance difference usually won't be significant. As ever for performance questions: when in doubt, measure!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLINQ Performance
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJon Skeet
UserOwnerUserId
1. USJon Skeet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI meant what it does behind the scenes. For example, i have an object collection. I can write a For loop which iterates through the entire collection and just checks the property for the value I need in each object or I can use LINQ. LINQ seems to be faster in many cases according to what I have read. My question is why is it faster and how is it doing the lookups?
 singulars
 PostPostId
 PO
 UserUserId
 USCrios
2. COLINQ won't usually be faster than the equivalent code - although I believe there are other projects to provide indexed lookups, for example. If you could give a concrete example where you expect LINQ to be faster, that would be helpful.
 singulars
 PostPostId
 PO
 UserUserId
 USJon Skeet

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.