StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4380047
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-12-07T18:11:17.563
FavoriteCount
0
LastActivityDate
2018-04-24T17:14:57.003
LastEditDate
2018-04-24T17:14:57.003
LastEditorUserId
2387977
OwnerUserId
153901
ParentId
479142
PostTypeId
2
Score
31
ViewCount
0
LastEditorDisplayName
text
Body
My two cents: An interface basically defines a contract, that any implementing class must adhere to(implement the interface members). It does not contain any code. On the other hand, an abstract class can contain code, and there might be some methods marked as abstract which an inheriting class must implement. The rare situations I've used abstract classes is when i have some default functionality that the inheriting class might not be interesting in overriding, in say an abstract base class, that some specialized classes inherit from. Example(a very rudimentary one!):Consider a base class called Customer which has abstract methods like <code>CalculatePayment()</code>, <code>CalculateRewardPoints()</code> and some non-abstract methods like <code>GetName()</code>, <code>SavePaymentDetails()</code>. Specialized classes like <code>RegularCustomer</code> and <code>GoldCustomer</code> will inherit from the <code>Customer</code> base class and implement their own <code>CalculatePayment()</code> and <code>CalculateRewardPoints()</code> method logic, but re-use the <code>GetName()</code> and <code>SavePaymentDetails()</code> methods. You can add more functionality to an abstract class(non abstract methods that is) without affecting child classes which were using an older version. Whereas adding methods to an interface would affect all classes implementing it as they would now need to implement the newly added interface members. An abstract class with all abstract members would be similar to an interface.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhen to use an interface instead of an abstract class and vice versa?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDherik
UserOwnerUserId
1. USPreethaA
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.