StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5494530
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-31T01:55:48.297
FavoriteCount
0
LastActivityDate
2011-03-31T02:41:22.253
LastEditDate
2011-03-31T02:41:22.253
LastEditorUserId
682970
OwnerUserId
682970
ParentId
5494481
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your explanation seems to point towards using an abstract class. You could have an abstract class that would have an implementation of the Initialize method, and you would not need to repeat it in the Oberon and AirSys subclasses. PullData could be an abstract method that would then get implemented in the separate subclasses. And yes, only the class that requires the ValidateData method would have it implemented. Example would be: <pre><code>public abstract class AirlineSystemBase { string Name { get; set; } int Code { get; set; } public void Initialize() { //code goes here } public abstract void PullData(); } public class Oberon : AirlineSystemBase { public override void PullData() { //code goes here } } public class AirSys : AirlineSystemBase { /// <summary> /// that is if say only AirSys class had a need for this ValidateData() method /// </summary> public void ValidateData() { //code goes here } public override void PullData() { //code goes here } } </code></pre> OR if you want to use both interface and abstract class: <pre><code>public interface IAirlineSystem { void PullData(); void ValidateData(); } public abstract class AirlineSystemBase : IAirlineSystem { string Name { get; set; } int Code { get; set; } public void Initialize() { //code goes here } public abstract void PullData(); public virtual void ValidateData() { //code goes here } } public class Oberon : AirlineSystemBase { public override void PullData() { //code goes here } } public class AirSys : AirlineSystemBase { /// <summary> /// that is if say only AirSys class had a need for this ValidateData() method /// </summary> public override void ValidateData() { //code goes here } public override void PullData() { //code goes here } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs an interface or an abstract class or both better in the following situation?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USZen Pak
UserOwnerUserId
1. USZen Pak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs an interface or an abstract class or both better in the following situation?
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.