StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6952805
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-05T07:20:28.360
FavoriteCount
0
LastActivityDate
2011-08-05T08:04:43.927
LastEditDate
2011-08-05T08:04:43.927
LastEditorUserId
404089
OwnerUserId
404089
ParentId
6952420
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Implementing an interface says HEY! LOOK AT ME! I CAN DO THIS. Interfaces lend themselves toward many applications: <ul> <li>Unit testing: If your methods accept interfaces as parameters, you can pass mock objects to test for bugs ensuring that any bugs found are not caused by bugs in the parameters.</li> <li>Code Reuse: You can make your code more generic if it uses interfaces, and more generic code lends itself to reuse. For example, UI Controls are highly reusable components which make use of interfaces such as INotifyPropertyChanged, which when implemented makes your custom classes work well with databinding.</li> <li>Software engineering best practice: It's good to separate the specification from the implementation because smarter, more experienced people said so. There are also plenty of good design patterns which require the use of interfaces.</li> <li>Mixins: Combined with extension methods you can use interfaces to implement quasi-mixins. When you implement that interface on a class, the class will inherit the relevant functionality. The best example I can think of here are the LINQ extension methods, which appply to classes which implement IEnumerable. Interfaces by themselves do not give us multiple inheritance, but mixins do.</li> <li>Crossing system boundaries: It's often nice to create interfaces for objects that you expect to cross system boundaries (i.e. web services). This can simplify serialisation and allows you to modify the concrete class without affecting the interface between two systems.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POinterface concept in C#
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USEvil Pigeon
UserOwnerUserId
1. USEvil Pigeon
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
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.