StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2803526
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-10T14:43:17.797
FavoriteCount
0
LastActivityDate
2010-05-10T14:53:24.860
LastEditDate
2010-05-10T14:53:24.860
LastEditorUserId
91671
OwnerUserId
91671
ParentId
2803312
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It seems that you want to have typesafety and LINQ support while simultaneously not defining the types involved - which you can't do in C#. One option is providing overloads of <code>Execute</code> that rather than taking <code>object ctx</code> can take the appropriate <code>IEnumerable<T></code> as a parameter? For instance, you could have several overloads: <pre><code>public override object Execute(Interpreter interpreter, IEnumerable<int> ctx) public override object Execute(Interpreter interpreter, IEnumerable<string> ctx) public override object Execute(Interpreter interpreter, IEnumerable<...> ctx) </code></pre> Alternatively, you could re-eimplement the LINQ methods you care about to work with plain <code>IEnumerable</code>. Doing so for FirstOrDefault is relatively easy: <pre><code>public static object FirstOrDefault( this IEnumerable sequence ) { if( sequence == null ) return null; using( var iter = sequence.GetEnumerator() ) { if( iter.MoveNext() ) return iter.Current; return null; } } </code></pre> Re-implementing all of LINQ against IEnumerable will not be fun ... or in some cases easy. Your best bet would be to create an adapter that allows you to treat <code>IEnumerable</code> as <code>IEnumerable<object></code> - then you can use it regardless of whether you're dealing with sequences of value types or reference types: <pre><code>public static IEnumerable<object> AsObjectSequence( this IEnumerable sequence ) { foreach( object x in sequence ) yield return x; } </code></pre> EDIT: It turns out, this is in principle, equivalent to using: <pre><code>sequence.Cast<object>() </code></pre> so yoy may want to use that, since it's more concise and directly built into LINQ.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing LINQ in generic collections
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLBushkin
UserOwnerUserId
1. USLBushkin
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
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.