StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11746813
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-07-31T18:40:27.703
FavoriteCount
0
LastActivityDate
2012-08-02T15:59:05.523
LastEditDate
2012-08-02T15:59:05.523
LastEditorUserId
77912
OwnerUserId
77912
ParentId
11746461
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
For your entity classes, I think you should leave the interface abstraction to the end, after you've defined all your business entities and can extrapolate a common behavior pattern among them. Only then can you infer a common interface among them. But your entity classes are ultimately concrete; there's no sense in trying to abstract them further. Ultimately changes to these concrete classes would require changes to the controllers/views also interacting with them. Don't fret over this. Once you've defined all your views for each entity, then you can start working out the abstractions, if there are any. If you have already defined your concrete entities, then you can start abstracting away for views. For a financial example, suppose I have a Trade class. Obviously I can have specific types of trades, such as a BondTrade, EquityTrade, etc. So I can also have a TradeView, which can have concrete views, i.e. BondTradeView, EquityTradeView, etc. You can have a higher level of abstraction, but ultimately, you'll need concrete classes that would define a specific view. <a href="http://sourcemaking.com/design_patterns/facade" rel="nofollow">Look at the Facade Design pattern as an example.</a> The facade can be used to create views based on your concrete implementations. It's a way of unifying all your concrete entities. It would contain the logic to know what view to create, and how, based on your entity. This would be a way to simplify the propagated changes done on your entities.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAvoid changes propagation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJose Chavez
UserOwnerUserId
1. USJose Chavez
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. This table or related slice is empty.
CommentsPostId
1. COActually, I already have defined all my business entities and I've got a quite good idea about how they will interact. So, you think that there's no way to prevent that a change in a concrete entity class propagates to many modules? Isn't this contrary to good design?
 singulars
 PostPostId
 PO
 UserUserId
 UStmh
2. COI went ahead and enlarged the answer, since it wouldn't fit in this comment box...
 singulars
 PostPostId
 PO
 UserUserId
 USJose Chavez

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.