StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHandling Transactions in DAO with an Injected iBATIS.NET SQL Mapper
primarykey
Id
3744255
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-09-19T01:58:58.017
FavoriteCount
0
LastActivityDate
2010-09-19T01:58:58.017
LastEditDate
LastEditorUserId
0
OwnerUserId
451693
ParentId
0
PostTypeId
1
Score
2
ViewCount
1088
LastEditorDisplayName
text
Body
I am currently using iBATIS.NET for a small application I am building. I like to create concrete Classes for my DAOs instead of using ISqlMapper directly and invoking named SQL statements. I am not using a Dependency Injection container of any sort, so ideally I have my DAOs set up as follows: <pre><code>public abstract class AbstractDAO { /// <summary> /// SQL Mapper. /// </summary> ISqlMapper mapper; /// <summary> /// Default Constructor. /// </summary> /// <param name="mapper"></param> public AbstractDAO(ISqlMapper mapper) { this.mapper = mapper; } } public class NodeDAO : AbstractDAO { /// <summary> /// Default Constructor. /// </summary> /// <param name="mapper"></param> public NodeDAO(ISqlMapper mapper) : base(mapper) { } /// <summary> /// Insert Node. /// </summary> /// <param name="node"></param> public void InsertNode(Node node) { // ... Assume Some Pretty Code. } } public class NodeRevisionDAO : AbstractDAO { /// <summary> /// Default Constructor. /// </summary> /// <param name="mapper"></param> public NodeRevisionDAO (ISqlMapper mapper) : base(mapper) { } /// <summary> /// Insert Node Revision. /// </summary> /// <param name="nodeRevision"></param> public void InsertNodeRevision(NodeRevision nodeRevision) { // ... Assume Some Pretty Code. } } </code></pre> From my main application code, let's say in some form of Business Layer, I would ideally call two insert Methods on the DAOs: <pre><code>// ... Assume DAOs are Initialized. nodeDAO.InsertNode(node); nodeRevisionDAO.InsertNodeRevision(nodeRevision); </code></pre> I want to make sure both statements are executed as an atomic operation in a transaction so that if either fails, both will be rolled back. But because the ISqlMapper is injected in both DAOs I have no control over the transactions. What would be the best approach to this problem? Putting it in another way, how can I handle transactions without exposing the ISqlMapper?
Tags
<c#><.net><dao><ibatis.net>
Title
Handling Transactions in DAO with an Injected iBATIS.NET SQL Mapper
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. US9ee1
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
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. VO
 singulars
 PostPostId
 POHandling Transactions in DAO with an Injected iBATIS.NET SQL Mapper
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI have the same design issue, except I'm not using SQLMapper, but my own interface that roughly encapsulates ADO.NET IDbConnection object
 singulars
 PostPostId
 POHandling Transactions in DAO with an Injected iBATIS.NET SQL Mapper
 UserUserId
 USdzendras
2. COFound answer to my problem here: http://stackoverflow.com/questions/773393/dao-pattern-where-do-transactions-fit-in
 singulars
 PostPostId
 POHandling Transactions in DAO with an Injected iBATIS.NET SQL Mapper
 UserUserId
 USdzendras

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.