StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
339659
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-04T05:23:54.720
FavoriteCount
0
LastActivityDate
2014-04-14T08:06:51.700
LastEditDate
2014-04-14T08:06:51.700
LastEditorUserId
764161
OwnerUserId
11388
ParentId
339639
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
Just to clarify there are differences between the concept of LINQ and LINQ to SQL. LINQ is a query syntax, not a language or an O/RM. You can build an O/RM on top of the syntax provided by LINQ. Since I gather that your question is really When to use LINQ to SQL I'll just address that. LINQ to SQL is best used when you are: <ul> <li>Only ever targeting MS SQL 2000+</li> <li>Doing RAD</li> </ul> I've used LINQ to SQL on a couple of commercial products and quite a few of my own products and found these benefits: <ul> <li>Familiar language to code in (C#/ VB.NET)</li> <li>Easier to maintain (we have more .NET than SQL gurus on staff)</li> <li>SQL generated is well structured and very optimal</li> <li>Allows direct translation of business rules to SQL while still keeping all business logic in a single project</li> </ul> As for LINQ as a concept I use it all the time, because I understand what it can/can't do and how to use it properly. Like any language feature it can be miss-used easily if people don't have an understanding of what it is and how to use it. I recommend the following blogs to get some of the concepts of LINQ down: <ul> <li><a href="http://blogs.bartdesmet.net/bart/" rel="nofollow noreferrer">Bart De Smet</a> - advanced</li> <li><a href="http://blogs.msdn.com/charlie/default.aspx" rel="nofollow noreferrer">Charlie Calvert</a></li> <li><a href="http://blogs.msdn.com/wriju/default.aspx" rel="nofollow noreferrer">Wriju</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy and When to use LINQ?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USComputer Scientist
UserOwnerUserId
1. USAaron Powell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy and When to use LINQ?
 singulars
 PostTypePostTypeId
 PTQuestion
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. This table or related slice is empty.

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.