StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhen using NHibernate and a unit-of-work-per-request, in what scenarios would it be beneficial to use multiple transactions per request?
primarykey
Id
3516821
data
AcceptedAnswerId
3518596
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-18T21:22:50.567
FavoriteCount
1
LastActivityDate
2010-08-20T17:53:56.473
LastEditDate
LastEditorUserId
0
OwnerUserId
171062
ParentId
0
PostTypeId
1
Score
3
ViewCount
303
LastEditorDisplayName
text
Body
In my web application a Session is created in the BeginRequest handler. All database operations are performed against this session. In the EndRequest handler, the session is used to create a transaction which is then committed. Afterward, the session is disposed. This wraps all database operations performed against the session into a single transaction. When is it beneficial to create a transaction to be committed within the request-transaction? How is this done? In other words, for what reason would I create a transaction for any purpose other than to commit all the database operations performed in the current request?
Tags
<asp.net><nhibernate>
Title
When using NHibernate and a unit-of-work-per-request, in what scenarios would it be beneficial to use multiple transactions per request?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStQuarella
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
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhen using NHibernate and a unit-of-work-per-request, in what scenarios would it be beneficial to use multiple transactions per request?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhen using NHibernate and a unit-of-work-per-request, in what scenarios would it be beneficial to use multiple transactions per request?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhen using NHibernate and a unit-of-work-per-request, in what scenarios would it be beneficial to use multiple transactions per request?
 UserUserId
 USPaco
 VoteTypeVoteTypeId
 VTFavorite
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.