StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs change-tracking in ORMs a necessity or a luxury, in the context of web apps?
primarykey
Id
1732755
data
AcceptedAnswerId
1734065
AnswerCount
8
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-11-14T00:29:06.523
FavoriteCount
0
LastActivityDate
2009-11-16T07:45:16.857
LastEditDate
2009-11-14T14:07:15.070
LastEditorUserId
39923
OwnerUserId
39923
ParentId
0
PostTypeId
1
Score
1
ViewCount
662
LastEditorDisplayName
text
Body
Since web applications are mostly stateless, and linear (request comes in, response goes out), is change-tracking really necessary? E.g. if I have an action that updates a <code>Product</code> instance I know at code-time what state I'm changing, I can just tell the repository "please update this instance". To clarify, my question is about the change-tracking feature of ORM products, such as LINQ to SQL, Entity Framework, and others.
Tags
<design-patterns><orm><ado.net>
Title
Is change-tracking in ORMs a necessity or a luxury, in the context of web apps?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMax Toro
UserOwnerUserId
1. USMax Toro
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POIs change-tracking in ORMs a necessity or a luxury, in the context of web apps?
 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.