StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20074102
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-19T14:25:43.973
FavoriteCount
0
LastActivityDate
2013-11-19T14:31:35.587
LastEditDate
2013-11-19T14:31:35.587
LastEditorUserId
122781
OwnerUserId
122781
ParentId
1344066
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I am planning my first N-tier architecture and came across this question just as I was about to post a similar one. All the sample code I’ve seen so far passes the entire object graph over the wire every time, without regard for what changes have actually been made. I've been considering to instead take the approach described above. Although, it appears to be the road less traveled. I like the idea of passing back just the deltas for each modified property. For collection properties, this would be what’s been both added and removed. For a single-valued property, it could be just the new value. I could implement this in a general way such that the accumulation of these deltas would be transparent for all domain objects. And the deltas would be sent across the wire in a general form, without using DTO classes specific to my domain model. This made me wonder if I couldn't take the idea further by also using the same general-purpose delta data structure for communication in the direction of server to client. After all, you could have a delta that basically populates an empty object. Then I could altogether eliminate the hard-coded DTO classes. I Googled "generic DTOs" (without quotes) and found <a href="http://www.adam-bien.com/roller/abien/entry/no_duplication_no_decoupling_the" rel="nofollow">this</a> and <a href="http://en.wikipedia.org/wiki/Service_Data_Objects" rel="nofollow">this</a>. Looks like others have already applied the idea in practice.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POcalculate object delta
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHappyNomad
UserOwnerUserId
1. USHappyNomad
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. 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.