StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14855236
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-13T13:58:04.560
FavoriteCount
0
LastActivityDate
2013-02-13T13:58:04.560
LastEditDate
LastEditorUserId
0
OwnerUserId
1111198
ParentId
14841543
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The DalManager (and the ConnectionManager) relies on reference counting to determine when close the actual connection. The rules are not making sure to dispose the DalManager and hence the DalManager and reference counting is off. Resulting in the update happening on a connection that was created and opened in one of the Fetch operations and is therefore not be enlisted in the TransactionScope on the Update method. See: <a href="http://msdn.microsoft.com/en-us/library/bb896149%28v=sql.100%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/bb896149%28v=sql.100%29.aspx</a> All rules must be changed to dispose of the DalManager. Original rule: <pre><code> protected override void Execute(RuleContext context) { var name = (string)context.InputPropertyValues[_nameProperty]; var id = (int)context.InputPropertyValues[_idProperty]; var dal = DalFactory.GetManager(); var countryDal = dal.GetProvider<ICountryDal>(); var exists = countryDal.Exists(id, name); if (exists) { context.AddErrorResult("Country with the same name already exists in the database."); } } </code></pre> DalManager is IDisposable but is not explicitly disposed here so it depends on when the GC will actually collect the object. Should be: <pre><code> protected override void Execute(RuleContext context) { var name = (string)context.InputPropertyValues[_nameProperty]; var id = (int)context.InputPropertyValues[_idProperty]; using (var dal = DalFactory.GetManager()) { var countryDal = dal.GetProvider<ICountryDal>(); var exists = countryDal.Exists(id, name); if (exists) { context.AddErrorResult("Country with the same name already exists in the database."); } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTransactionScope doesn't rollback on exception CSLA 4.3
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMensur
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTransactionScope doesn't rollback on exception CSLA 4.3
 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
 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.