I too would like the ability to determine if a transaction is already open. I assumed that functionality existed but see the same issues that Samuel is facing.
What is the "iBatis method" of checking for an open transaction? On 2/21/07, Clough, Samuel (USPC.PRG.Atlanta) <[EMAIL PROTECTED]> wrote:
I'm not sure that will help though. The IDbConnection interface does not offer any help as to whether there is an open transaction and IDbTransaction does not offer any state information. As I mentioned, I can't rely on the presence of an transaction object either because it's not set to null after a commit in iBatis. Is there some reason we can't add the propery to expose the session variable like I mentioned before? This seems like it would be a common problem. ________________________________ From: Gilles Bayon [mailto:[EMAIL PROTECTED] Sent: Sunday, February 18, 2007 12:08 PM To: [email protected] Subject: Re: Checking for Open Transactions On the ISqlMapper, you can access the ISqlMapSession (the current SqlMap session) which will give you access to the underlying IDbConnection and IDbTransaction. ________________________________ Princeton Retirement Group, Inc - Important Terms This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location. This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail. ________________________________
