StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12445376
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-09-16T08:12:53.837
FavoriteCount
0
LastActivityDate
2012-09-16T08:12:53.837
LastEditDate
LastEditorUserId
0
OwnerUserId
1430156
ParentId
12445099
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Depending on the length of your method, this may be a situation for polymorphism: As noted in other answers, <code>string</code> and <code>StringBuilder</code> are not related to each other. Therefore, your only chance to use the same method on them is to create wrappers for these two types which are related. You could define a wrapper base class with your method like this: <pre><code>public abstract class ScannableStringBase { public abstract int Length { get; } public abstract char this[int index] { get; } public int PositionOfTheSecondWord() { int pos = 0; int state = 0; char c; int length = this.Length; while (pos <= length - 1) { c = this[pos]; if (c == ' ' || c == '\n') // space { if (state == 1) state = 2; // 2 means the space between the first and the second word has begun } else // a letter if (state == 0) state = 1; // 1 means the first word has begun if (state == 2) return pos; pos++; } return -1; } } </code></pre> From that class, derive subclasses that handle the desired value types: <pre><code>public class ScannableString : ScannableStringBase { public ScannableString(string value) { this.stringValue = value; } private readonly string stringValue; public override int Length { get { return stringValue.Length; } } public override char this[int index] { get { return stringValue[index]; } } } public class ScannableStringBuilder : ScannableStringBase { public ScannableString(stringBuilder value) { this.stringBuilder = value; } private readonly string stringBuilder; public override int Length { get { return stringBuilder.Length; } } public override char this[int index] { get { return stringBuilder[index]; } } } </code></pre> Summarizing, you get: <ul> <li>No code duplication, because <code>PositionOfTheSecondWord()</code> is only defined once, in the base class.</li> <li>Type-safety, because your <code>PositionOfTheSecondWord()</code> method cannot be called on anything other than <code>string</code> or <code>StringBuilder</code>.</li> <li>Extensibility, because if you ever discover you want to support a third type, you can simply derive yet another class from <code>ScannableStringBase</code>.</li> </ul> One possible drawback may be that you have to distinguish between the type to analyze somewhere beforehand, so you can decide whether to instantiate a <code>ScannableString</code> or a <code>ScannableStringBuilder</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGeneric method with an argument of two possible types sharing common methods
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USO. R. Mapper
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGeneric method with an argument of two possible types sharing common methods
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThank you very much for your detailed answer! It is certainly a solution. It is sad though C# doesn't provide simpler means for the task.
 singulars
 PostPostId
 PO
 UserUserId
 USInego
2. CO@Inego: Indeed, sometimes I too wish for implicit interfaces and according generic constraints.
 singulars
 PostPostId
 PO
 UserUserId
 USO. R. Mapper

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.