StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15585440
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-23T09:59:01.190
FavoriteCount
0
LastActivityDate
2013-03-23T10:07:51.450
LastEditDate
2013-03-23T10:07:51.450
LastEditorUserId
701054
OwnerUserId
701054
ParentId
15585358
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Passing in a method as a parameter can be used to prevent dependencies and coupling. Let's take a look at how this can be used for the Strategy pattern: Let's say we have a method <code>PrintReport</code>, which prints a given list of items, which might be sorted by Name or by Type, based on a parameter. This is the naive approach: <pre><code>public void PrintReport (List<Item> data, SortOrder sortBy) { List<Item> sortedItems; switch (sortBy) { case SortOrder.Name: sortedItems = SortByName(data); break; case SortOrder.Type: sortedItems = SortByType(data); break; } Print(sortedItems); } </code></pre> It's simple but it works. But what happens when we want to add a new sort order? We need to update the SortOrder enum, go into <code>PrintReport</code> and add a new <code>case</code> and call the new <code>SortByWhatever</code> method. But if we passed in a method as a parameter, our <code>PrintReport</code> can be simpler and not care about the sort implementation: <pre><code>public void PrintReport (List<Item> data, Func<List<Item>, List<Item>> sorter) { List<Item> sortedItems = sorter(data); Print(sortedItems); } </code></pre> Now the sorting function can be defined anyway, possibly even in a different assembly that <code>PrintReport</code> isn't even aware of. It can be a lambda function or an anonymous method defined ad-hoc. But in all cases, our method will receive the delegate, use it to sort, and then print the report. Here's a usage example. At first it looks like we merely moved the switch/case outside of the function, which is important enough since it allows different callers to have different logic. But watch for the third case. <pre><code>public void HandleData() { switch (ReportItemOrder) { case SortOrder.Name: PrintReport(data, SortByName); break; case SortOrder.Type: PrintReport(data, SortByType); break; case SortOrder.Whatever: Func<List<Item>, List<Item>> customSort = (items) => /* do something */; PrintReport(data, customSort); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing methods as parameter vs calling methods directly
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAvner Shahar-Kashtan
UserOwnerUserId
1. USAvner Shahar-Kashtan
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
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.