StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11899258
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-08-10T09:54:18.390
FavoriteCount
0
LastActivityDate
2012-08-10T13:41:54.207
LastEditDate
2012-08-10T13:41:54.207
LastEditorUserId
1105881
OwnerUserId
1105881
ParentId
11898957
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Update: please read clarification in the end of answer for details about closure handling. First things first. This code: <pre><code> for (int i = 0; i < driveList.Count; i++) { var q = from sd in db.ServerDrives where sd.DriveLetter == driveList[i].Name select sd; //... } </code></pre> won't work irregardless of curly braces. The reason for that is closure of <code>i</code> (which is masked out by funny LINQ syntax). The easiest way to fix it is to store <code>i</code> value (or referenced value) in separate variable. <pre><code> for (int i = 0; i < driveList.Count; i++) { var j = i; var q = from sd in db.ServerDrives where sd.DriveLetter == driveList[j].Name select sd; //... } </code></pre> This will work, but it looks loosy. Better: <pre><code> for (int i = 0; i < driveList.Count; i++) { var drive = driveList[i]; var q = from sd in db.ServerDrives where sd.DriveLetter == drive.Name select sd; ServerDrive existingServerDrives = q.First(); existingServerDrives.FreeSpace = drive.FreeSpace; //.. db.SubmitChanges(); } </code></pre> But why would you need loop in first place? Why not <code>foreach</code>? <pre><code> foreach (var drive in driveList) { var q = from sd in db.ServerDrives where sd.DriveLetter == drive.Name select sd; ServerDrive existingServerDrives = q.First(); existingServerDrives.FreeSpace = drive.FreeSpace; //.. db.SubmitChanges(); } </code></pre> But this won't work too, be careful. Same trouble with closures. Solution is easy: <pre><code> foreach (var d in driveList) { var drive = d; var q = from sd in db.ServerDrives where sd.DriveLetter == drive.Name select sd; ServerDrive existingServerDrives = q.First(); existingServerDrives.FreeSpace = drive.FreeSpace; //.. db.SubmitChanges(); } </code></pre> But of course such things are better with projections: <pre><code> foreach (var d in driveList.Select(d => new {freeSpace = d.FreeSpace, existingServerDrives = db.ServerDrives.First(sd => sd.DriveLetter == d.Name)})) { d.existingServerDrives.FreeSpace = d.freeSpace; //.. db.SubmitChanges(); } </code></pre> Clarification: In fact, I am not completely right about "will not work" part. It will if <code>driveList</code> is <code>IQueryable</code>, but it won't if it is <code>IEnumerable</code> (because the former uses expressions, and the latter - delegates). But because syntax is same, it is all too easy to make this error, so you still should not use loop variables inside lambda expressions irregardless of their real type.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC# - SQL - LINQ Query
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSerg Rogovtsev
UserOwnerUserId
1. USSerg Rogovtsev
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
CommentsPostId

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.